From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Philipp Zabel <p.zabel@pengutronix•de>,
Bartosz Golaszewski <bartosz.golaszewski@linaro•org>
Cc: Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: Re: linux-next: build failure after merge of the reset tree
Date: Fri, 21 Nov 2025 14:50:42 +1100 [thread overview]
Message-ID: <20251121145042.3cef6e7a@canb.auug.org.au> (raw)
In-Reply-To: <20251121111534.7cdbfe5c@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 2229 bytes --]
Hi all,
On Fri, 21 Nov 2025 11:15:34 +1100 Stephen Rothwell <sfr@canb•auug.org.au> wrote:
>
> After merging the reset tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> drivers/platform/x86/intel/chtwc_int33fe.c:80:12: error: 'struct software_node_ref_args' has no member named 'node'; did you mean 'swnode'?
> 80 | { .node = NULL },
> | ^~~~
> | swnode
> drivers/platform/x86/intel/chtwc_int33fe.c: In function 'cht_int33fe_remove_nodes':
> drivers/platform/x86/intel/chtwc_int33fe.c:193:33: error: 'struct software_node_ref_args' has no member named 'node'; did you mean 'swnode'?
> 193 | if (fusb302_mux_refs[0].node) {
> | ^~~~
> | swnode
> drivers/platform/x86/intel/chtwc_int33fe.c:194:76: error: 'struct software_node_ref_args' has no member named 'node'; did you mean 'swnode'?
> 194 | fwnode_handle_put(software_node_fwnode(fusb302_mux_refs[0].node));
> | ^~~~
> | swnode
> drivers/platform/x86/intel/chtwc_int33fe.c:195:37: error: 'struct software_node_ref_args' has no member named 'node'; did you mean 'swnode'?
> 195 | fusb302_mux_refs[0].node = NULL;
> | ^~~~
> | swnode
> drivers/platform/x86/intel/chtwc_int33fe.c: In function 'cht_int33fe_add_nodes':
> drivers/platform/x86/intel/chtwc_int33fe.c:225:29: error: 'struct software_node_ref_args' has no member named 'node'; did you mean 'swnode'?
> 225 | fusb302_mux_refs[0].node = mux_ref_node;
> | ^~~~
> | swnode
>
> Caused by commit
>
> d7cdbbc93c56 ("software node: allow referencing firmware nodes")
>
> I have used the reset tree from next-20251120 for today.
This same commit is also in the gpio-brgl tree, so I have used that
tree from next-20251120 as well.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2025-11-21 3:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-21 0:15 linux-next: build failure after merge of the reset tree Stephen Rothwell
2025-11-21 3:50 ` Stephen Rothwell [this message]
2025-11-21 8:22 ` Philipp Zabel
2025-11-21 9:15 ` Bartosz Golaszewski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20251121145042.3cef6e7a@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=bartosz.golaszewski@linaro$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=p.zabel@pengutronix$(echo .)de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox