[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YtHBvb/kh/Sl0cmz@smile.fi.intel.com>
Date: Fri, 15 Jul 2022 22:36:29 +0300
From: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To: Marcin Wojtas <mw@...ihalf.com>
Cc: linux-kernel@...r.kernel.org, linux-acpi@...r.kernel.org,
netdev@...r.kernel.org, rafael@...nel.org, sean.wang@...iatek.com,
Landen.Chao@...iatek.com, linus.walleij@...aro.org, andrew@...n.ch,
vivien.didelot@...il.com, f.fainelli@...il.com, olteanv@...il.com,
davem@...emloft.net, edumazet@...gle.com, kuba@...nel.org,
pabeni@...hat.com, linux@...linux.org.uk, hkallweit1@...il.com,
gjb@...ihalf.com, jaz@...ihalf.com, tn@...ihalf.com,
Samer.El-Haj-Mahmoud@....com, upstream@...ihalf.com
Subject: Re: [net-next: PATCH v2 5/8] device property: introduce
fwnode_dev_node_match
On Fri, Jul 15, 2022 at 10:50:09AM +0200, Marcin Wojtas wrote:
> This patch adds a new generic routine fwnode_dev_node_match
> that can be used e.g. as a callback for class_find_device().
> It searches for the struct device corresponding to a
> struct fwnode_handle by iterating over device and
> its parents.
Implementation
1) misses the word 'parent';
2) located outside of the group of fwnode APIs operating on parents.
I would suggest to rename to fwnode_get_next_parent_node() and place
near to fwnode_get_next_parent_dev() (either before or after, where
it makes more sense).
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists