From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: "Jean-François Lessard" <jefflessard3@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Danilo Krummrich <dakr@kernel.org>,
Daniel Scally <djrscally@gmail.com>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] device property: Add scoped fwnode child node iterators
Date: Mon, 1 Sep 2025 09:11:03 +0300 [thread overview]
Message-ID: <aLU497rXkuHtTl43@smile.fi.intel.com> (raw)
In-Reply-To: <AA99AF86-CD2A-4BBE-92BC-3D9005E7BA3B@gmail.com>
On Fri, Aug 29, 2025 at 07:34:17AM -0400, Jean-François Lessard wrote:
> Le 29 août 2025 00 h 23 min 22 s HAE, Greg Kroah-Hartman <gregkh@linuxfoundation.org> a écrit :
> >On Thu, Aug 28, 2025 at 10:17:59PM -0400, Jean-François Lessard wrote:
...
> >We need a real user of this before we can add them, so please do that as
> >part of a patch series.
> >
>
> I understand the "no dead code" policy, but I found existing manual
> implementations of this exact pattern in the current kernel.
>
> For example, drivers/i2c/i2c-core-slave.c already does:
>
> struct fwnode_handle *child __free(fwnode_handle) = NULL;
> ...
> fwnode_for_each_child_node(fwnode, child) {
> ...
> }
>
> This suggests developers are already wanting this functionality but
> implementing it manually.
>
> If included with my driver series, I would only add the
> fwnode_for_each_available_child_node_scoped() variant that I actually use,
I fully agree with Greg, please make it series out of two, I will review both
as soon as it appears in my mailbox.
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2025-09-01 6:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-29 2:17 Jean-François Lessard
2025-08-29 4:23 ` Greg Kroah-Hartman
2025-08-29 11:34 ` Jean-François Lessard
2025-08-29 11:39 ` Greg Kroah-Hartman
2025-09-01 6:11 ` Andy Shevchenko [this message]
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=aLU497rXkuHtTl43@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=dakr@kernel.org \
--cc=djrscally@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=jefflessard3@gmail.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--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
all inboxes | Powered by JetHome®