[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Z_U3VcFg0ZtSnLcg@smile.fi.intel.com>
Date: Tue, 8 Apr 2025 17:48:53 +0300
From: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To: Sakari Ailus <sakari.ailus@...ux.intel.com>
Cc: Mauro Carvalho Chehab <mchehab+huawei@...nel.org>,
Tomi Valkeinen <tomi.valkeinen@...asonboard.com>,
Jai Luthra <jai.luthra@...asonboard.com>,
Wolfram Sang <wsa+renesas@...g-engineering.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 v3 0/7] i2c: core: Move client towards fwnode
On Tue, Apr 08, 2025 at 02:43:40PM +0000, Sakari Ailus wrote:
> On Mon, Apr 07, 2025 at 06:44:56PM +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.
> >
> > Tomi tested the last patch, but since it was separate there is no tag (yet).
>
> Apart from the two minor commit message comments:
>
> Reviewed-by: Sakari Ailus <sakari.ailus@...ux.intel.com>
Thank you for your review!
Does it imply that media patch can go via I²C subsystem?
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists