linux-kernel - Re: linux-next: build failure after merge of the devicetree-fixes 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] [day] [month] [year] [list]

Message-ID: <CAL_JsqK22+X3aO==2NU1R1WAHwUf5sPCszYDHEYDF__B98OJLA@mail.gmail.com>
Date: Mon, 17 Nov 2025 16:57:41 -0600
From: Rob Herring <robh@...nel.org>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Herve Codina <herve.codina@...tlin.com>, Saravana Kannan <saravanak@...gle.com>, 
	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 devicetree-fixes tree

On Mon, Nov 17, 2025 at 4:39 PM Stephen Rothwell <sfr@...b.auug.org.au> wrote:
>
> Hi all,
>
> After merging the devicetree-fixes tree, today's linux-next build
> (powerpc ppc64_defconfig) failed like this:
>
> drivers/base/core.c: In function 'fw_devlink_refresh_fwnode':
> drivers/base/core.c:269:23: error: implicit declaration of function 'get_device_from_fwnode'; did you mean 'get_dev_from_fwnode'? [-Wimplicit-function-declaration]
>   269 |                 dev = get_device_from_fwnode(fwnode);
>       |                       ^~~~~~~~~~~~~~~~~~~~~~
>       |                       get_dev_from_fwnode
> drivers/base/core.c:269:21: error: assignment to 'struct device *' from 'int' makes pointer from integer without a cast [-Wint-conversion]
>   269 |                 dev = get_device_from_fwnode(fwnode);
>       |                     ^
>
> Caused by commit
>
>   227c4e0e70fe ("of: dynamic: Fix overlayed devices not probing because of fw_devlink")
>
> I have used the devicetree-fixes tree from next-20251117 for today.

Sorry about that, I should have found that. Now fixed by reverting to
the old name.

Rob