linux-kernel - Re: linux-next: build failure after merge of the pinctrl tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <DBBN42KD0D2L.10BGEGJJ5XH0J@fairphone.com>
Date: Mon, 14 Jul 2025 10:37:36 +0200
From: "Luca Weiss" <luca.weiss@...rphone.com>
To: "Stephen Rothwell" <sfr@...b.auug.org.au>, "Linus Walleij"
 <linus.walleij@...aro.org>
Cc: "Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>, "Linux Next
 Mailing List" <linux-next@...r.kernel.org>
Subject: Re: linux-next: build failure after merge of the pinctrl tree

On Mon Jul 14, 2025 at 9:08 AM CEST, Stephen Rothwell wrote:
> Hi all,
>
> After merging the pinctrl tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> drivers/pinctrl/qcom/pinctrl-milos.c:1323:19: error: 'msm_pinctrl_remove' undeclared here (not in a function); did you mean 'msm_pinctrl_probe'?
>  1323 |         .remove = msm_pinctrl_remove,
>       |                   ^~~~~~~~~~~~~~~~~~
>       |                   msm_pinctrl_probe
>
> Caused by commit
>
>   b614f176b308 ("pinctrl: qcom: Add Milos pinctrl driver")
>
> I have used the pinctrl tree from next-20250711 for today.

This seems to be the for-next/devel branch not containing a commit from
fixes. I'll let Linus sort this out, just needs one line to be removed
from pinctrl-milos.c as per
https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl.git/commit/?h=56ec63a6e107e724619e61c7e605b49d365dfa07

Regards
Luca