[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <Z__tXkgOhvJUIYXq@smile.fi.intel.com>
Date: Wed, 16 Apr 2025 20:48:14 +0300
From: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To: Wolfram Sang <wsa+renesas@...g-engineering.com>,
Sakari Ailus <sakari.ailus@...ux.intel.com>,
Tomi Valkeinen <tomi.valkeinen@...asonboard.com>,
Mauro Carvalho Chehab <mchehab+huawei@...nel.org>,
Jai Luthra <jai.luthra@...asonboard.com>, linux-i2c@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-media@...r.kernel.org,
Mauro Carvalho Chehab <mchehab@...nel.org>
Subject: Re: [PATCH v5 0/7] i2c: core: Move client towards fwnode
On Wed, Apr 16, 2025 at 06:11:02PM +0200, Wolfram Sang wrote:
> On Wed, Apr 16, 2025 at 10:01:30AM +0300, Andy Shevchenko wrote:
> > The struct i2c_board_info has of_node and fwnode members. This is quite
> > confusing as they are of the same semantics and it's tend to have an issue
> > if user assigns both. Luckily there is only a single driver that does this
> > and fix is provided in the last patch. Nevertheless the series moves
> > the client handling code to use fwnode and deprecates the of_node member
> > in the respective documentation.
...
> Works at least on my OF-based platform. Let's go CI.
>
> Applied to for-next, thanks!
Thank you!
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists