From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: "Jean-François Lessard" <jefflessard3@gmail.com>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Daniel Scally <djrscally@gmail.com>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Danilo Krummrich <dakr@kernel.org>,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-acpi@vger.kernel.org
Subject: Re: [PATCH v4 1/2] device property: Add scoped fwnode child node iterators
Date: Thu, 25 Sep 2025 22:43:05 +0200 [thread overview]
Message-ID: <aNWpWdLJUJP-cdoq@shikoro> (raw)
In-Reply-To: <20250902190443.3252-2-jefflessard3@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 930 bytes --]
On Tue, Sep 02, 2025 at 03:04:39PM -0400, Jean-François Lessard wrote:
> Add scoped versions of fwnode child node iterators that automatically
> handle reference counting cleanup using the __free() attribute:
>
> - fwnode_for_each_child_node_scoped()
> - fwnode_for_each_available_child_node_scoped()
>
> These macros follow the same pattern as existing scoped iterators in the
> kernel, ensuring fwnode references are automatically released when the
> iterator variable goes out of scope. This prevents resource leaks and
> eliminates the need for manual cleanup in error paths.
>
> The implementation mirrors the non-scoped variants but uses
> __free(fwnode_handle) for automatic resource management, providing a
> safer and more convenient interface for drivers iterating over firmware
> node children.
>
> Signed-off-by: Jean-François Lessard <jefflessard3@gmail.com>
Applied to for-next, thanks!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2025-09-25 20:43 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-02 19:04 [PATCH v4 0/2] device property: Add scoped fwnode child node iterators Jean-François Lessard
2025-09-02 19:04 ` [PATCH v4 1/2] " Jean-François Lessard
2025-09-02 19:11 ` Danilo Krummrich
2025-09-03 10:29 ` Andy Shevchenko
2025-09-03 13:18 ` Sakari Ailus
2025-09-03 16:43 ` Jean-François Lessard
2025-09-03 17:22 ` Danilo Krummrich
2025-09-04 5:56 ` Sakari Ailus
2025-09-04 7:03 ` Danilo Krummrich
2025-09-04 7:43 ` Sakari Ailus
2025-09-04 8:51 ` Danilo Krummrich
2025-09-04 11:54 ` Sakari Ailus
2025-09-04 12:39 ` Sakari Ailus
2025-09-04 16:14 ` Danilo Krummrich
2025-09-16 16:18 ` Sakari Ailus
2025-09-25 20:43 ` Wolfram Sang [this message]
2025-09-02 19:04 ` [PATCH v4 2/2] i2c: core: Use fwnode_for_each_child_node_scoped() Jean-François Lessard
2025-09-03 13:19 ` Sakari Ailus
2025-09-25 20:43 ` Wolfram Sang
2025-09-03 10:30 ` [PATCH v4 0/2] device property: Add scoped fwnode child node iterators Andy Shevchenko
2025-09-04 9:49 ` Wolfram Sang
2025-09-04 9:59 ` Andy Shevchenko
2025-09-04 10:13 ` Danilo Krummrich
2025-09-04 10:38 ` Sakari Ailus
2025-09-10 12:53 ` Wolfram Sang
2025-09-12 22:28 ` Wolfram Sang
2025-09-15 6:27 ` Andy Shevchenko
2025-09-25 10:54 ` Wolfram Sang
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=aNWpWdLJUJP-cdoq@shikoro \
--to=wsa+renesas@sang-engineering.com \
--cc=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-i2c@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