From: "Danilo Krummrich" <dakr@kernel.org>
To: "Jiawen Wu" <jiawenwu@trustnetic.com>
Cc: "'Bartosz Golaszewski'" <brgl@kernel.org>,
"'Bartosz Golaszewski'" <bartosz.golaszewski@linaro.org>,
<andriy.shevchenko@linux.intel.com>, <andy@kernel.org>,
<broonie@kernel.org>, <ckeepax@opensource.cirrus.com>,
<david.rhodes@cirrus.com>, <djrscally@gmail.com>,
<gregkh@linuxfoundation.org>, <heikki.krogerus@linux.intel.com>,
<krzk@kernel.org>, <linus.walleij@linaro.org>,
<linux-acpi@vger.kernel.org>, <linux-gpio@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <linux-sound@vger.kernel.org>,
<linux-spi@vger.kernel.org>, <mstrozek@opensource.cirrus.com>,
<p.zabel@pengutronix.de>, <patches@opensource.cirrus.com>,
<rafael@kernel.org>, <rf@opensource.cirrus.com>,
<sakari.ailus@linux.intel.com>
Subject: Re: [PATCH v7 3/9] software node: allow referencing firmware nodes
Date: Tue, 23 Dec 2025 11:41:52 +0100 [thread overview]
Message-ID: <DF5J7H0BSBTK.362ZAJTRBK6U1@kernel.org> (raw)
In-Reply-To: <030101dc73f1$46a62b40$d3f281c0$@trustnetic.com>
On Tue Dec 23, 2025 at 10:48 AM CET, Jiawen Wu wrote:
> On Tue, Dec 23, 2025 5:37 PM, Bartosz Golaszewski wrote:
>> On Tue, Dec 23, 2025 at 9:44 AM Jiawen Wu <jiawenwu@trustnetic.com> wrote:
>> > And I temporarily added this line to fix it:
>> >
>> > diff --git a/include/linux/property.h b/include/linux/property.h
>> > index 272bfbdea7bf..e30ef23a9af3 100644
>> > --- a/include/linux/property.h
>> > +++ b/include/linux/property.h
>> > @@ -371,6 +371,7 @@ struct software_node_ref_args {
>> > (const struct software_node_ref_args) { \
>> > .swnode = _Generic(_ref_, \
>> > const struct software_node *: _ref_, \
>> > + struct software_node *: _ref_, \
>> > default: NULL), \
>> > .fwnode = _Generic(_ref_, \
>> > struct fwnode_handle *: _ref_, \
>> >
>>
>> Ah I see, we'd assign struct software_node * to const struct
>> software_node * and it used to work but with _Generic() we need the
>> exact type. I agree with this approach, do you want to send a proper
>> patch?
>
> It might be more appropriate for you to send the patch, and could also
> check if there are any other missed details, like for fwnode...
> I'm not very proficient in this field. :)
There is already [1], which I queued up in the driver-core tree to send as fix
for -rc3.
[1] https://lore.kernel.org/lkml/20251219083638.2454138-1-sakari.ailus@linux.intel.com/
next prev parent reply other threads:[~2025-12-23 10:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-23 7:39 [PATCH v7 3/9] software node: allow referencing firmware nodes Jiawen Wu
2025-12-23 8:09 ` Bartosz Golaszewski
2025-12-23 8:44 ` Jiawen Wu
2025-12-23 9:36 ` Bartosz Golaszewski
2025-12-23 9:48 ` Jiawen Wu
2025-12-23 10:41 ` Danilo Krummrich [this message]
2025-12-24 1:59 ` Jiawen Wu
-- strict thread matches above, loose matches on Subject: below --
2025-11-20 13:23 [PATCH v7 0/9] reset: rework reset-gpios handling Bartosz Golaszewski
2025-11-20 13:23 ` [PATCH v7 3/9] software node: allow referencing firmware nodes Bartosz Golaszewski
2025-11-20 13:27 ` Charles Keepax
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=DF5J7H0BSBTK.362ZAJTRBK6U1@kernel.org \
--to=dakr@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=andy@kernel.org \
--cc=bartosz.golaszewski@linaro.org \
--cc=brgl@kernel.org \
--cc=broonie@kernel.org \
--cc=ckeepax@opensource.cirrus.com \
--cc=david.rhodes@cirrus.com \
--cc=djrscally@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=jiawenwu@trustnetic.com \
--cc=krzk@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=mstrozek@opensource.cirrus.com \
--cc=p.zabel@pengutronix.de \
--cc=patches@opensource.cirrus.com \
--cc=rafael@kernel.org \
--cc=rf@opensource.cirrus.com \
--cc=sakari.ailus@linux.intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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