[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <172407794569.198441.3395176443590632204.b4-ty@arm.com>
Date: Mon, 19 Aug 2024 15:33:34 +0100
From: Suzuki K Poulose <suzuki.poulose@....com>
To: Michal Simek <michal.simek@....com>,
Michael Hennerich <Michael.Hennerich@...log.com>,
James Clark <james.clark@...aro.org>,
Javier Carrasco <javier.carrasco.cruz@...il.com>,
Lars-Peter Clausen <lars@...afoo.de>,
Pavel Machek <pavel@....cz>,
Mike Leach <mike.leach@...aro.org>,
Sakari Ailus <sakari.ailus@...ux.intel.com>,
Anand Ashok Dumbre <anand.ashok.dumbre@...inx.com>,
Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
Lee Jones <lee@...nel.org>,
Jonathan Cameron <jic23@...nel.org>
Cc: Suzuki K Poulose <suzuki.poulose@....com>,
linux-kernel@...r.kernel.org,
coresight@...ts.linaro.org,
linux-iio@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
linux-leds@...r.kernel.org
Subject: Re: [PATCH v2 0/3] use device_for_each_child_node_scoped to access device child nodes
On Thu, 08 Aug 2024 17:12:36 +0200, Javier Carrasco wrote:
> This series removes accesses to the device `fwnode` to iterate over its
> own child nodes. Using the `device_for_each_child_node` macro provides
> direct access to the device child nodes, and given that in all cases
> they are only required within the loop, the scoped variant of the macro
> can be used.
>
> It has been stated in previous discussions [1] that `device_for_each_*`
> should be used to access device child nodes, removing the need to access
> its internal fwnode, and restricting `fwnode_for_each_*` to traversing
> subnodes when required.
>
> [...]
Applied, to coresight next tree. Thanks!
[1/3] coresight: cti: use device_* to iterate over device child nodes
https://git.kernel.org/coresight/c/daca644d0c9e0
Best regards,
--
Suzuki K Poulose <suzuki.poulose@....com>
Powered by blists - more mailing lists