From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>,
Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
Jai Luthra <jai.luthra@ideasonboard.com>,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-media@vger.kernel.org,
Mauro Carvalho Chehab <mchehab@kernel.org>
Subject: Re: [PATCH v5 0/7] i2c: core: Move client towards fwnode
Date: Wed, 16 Apr 2025 20:48:14 +0300 [thread overview]
Message-ID: <Z__tXkgOhvJUIYXq@smile.fi.intel.com> (raw)
In-Reply-To: <Z__Wlri8-tjuctsa@shikoro>
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
prev parent reply other threads:[~2025-04-16 17:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-16 7:01 [PATCH v5 0/7] i2c: core: Move client towards fwnode Andy Shevchenko
2025-04-16 7:01 ` [PATCH v5 1/7] i2c: core: Drop duplicate check before calling OF APIs Andy Shevchenko
2025-04-16 7:01 ` [PATCH v5 2/7] i2c: core: Unify the firmware node type check Andy Shevchenko
2025-04-16 7:01 ` [PATCH v5 3/7] i2c: core: Switch to fwnode APIs to get IRQ Andy Shevchenko
2025-04-16 7:01 ` [PATCH v5 4/7] i2c: core: Reuse fwnode variable where it makes sense Andy Shevchenko
2025-04-16 7:01 ` [PATCH v5 5/7] i2c: core: Do not dereference fwnode in struct device Andy Shevchenko
2025-04-16 7:01 ` [PATCH v5 6/7] i2c: core: Deprecate of_node in struct i2c_board_info Andy Shevchenko
2025-04-16 7:01 ` [PATCH v5 7/7] media: i2c: ds90ub960: Remove of_node assignment Andy Shevchenko
2025-04-16 16:11 ` [PATCH v5 0/7] i2c: core: Move client towards fwnode Wolfram Sang
2025-04-16 17:48 ` Andy Shevchenko [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=Z__tXkgOhvJUIYXq@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=jai.luthra@ideasonboard.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=mchehab@kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=tomi.valkeinen@ideasonboard.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.