From: "Jean-François Lessard" <jefflessard3@gmail.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Wolfram Sang <wsa+renesas@sang-engineering.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 v3 2/2] i2c: core: Use fwnode_for_each_child_node_scoped()
Date: Tue, 02 Sep 2025 12:56:25 -0400 [thread overview]
Message-ID: <AB7B668E-107D-43E6-A9F7-57F5F9FADD2A@gmail.com> (raw)
In-Reply-To: <aLa8lGxHvCd6nreg@smile.fi.intel.com>
Le 2 septembre 2025 05 h 44 min 52 s HAE, Andy Shevchenko <andriy.shevchenko@linux.intel.com> a écrit :
>On Mon, Sep 01, 2025 at 12:36:45PM -0400, Jean-François Lessard wrote:
>> Replace the manual __free(fwnode_handle) iterator declaration with the
>> new scoped iterator macro for cleaner, less error-prone code.
>>
>> This eliminates the need for explicit iterator variable declaration with
>> the cleanup attribute, making the code more consistent with other scoped
>> iterator usage patterns in the kernel.
>
>Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
>
Acknowledged with thanks. Will add this tag in the next submission.
prev parent reply other threads:[~2025-09-02 16:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-01 16:36 [PATCH v3 0/2] device property: Add scoped fwnode child node iterators Jean-François Lessard
2025-09-01 16:36 ` [PATCH v3 1/2] " Jean-François Lessard
2025-09-01 17:48 ` Danilo Krummrich
2025-09-01 18:16 ` Jean-François Lessard
2025-09-02 4:50 ` Greg Kroah-Hartman
2025-09-02 16:54 ` Jean-François Lessard
2025-09-01 16:36 ` [PATCH v3 2/2] i2c: core: Use fwnode_for_each_child_node_scoped() Jean-François Lessard
2025-09-02 9:44 ` Andy Shevchenko
2025-09-02 16:56 ` Jean-François Lessard [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=AB7B668E-107D-43E6-A9F7-57F5F9FADD2A@gmail.com \
--to=jefflessard3@gmail.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=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 \
--cc=wsa+renesas@sang-engineering.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