From: "Uwe Kleine-König (The Capable Hub)" <u.kleine-koenig@baylibre.com>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Andi Shyti <andi.shyti@kernel.org>,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
Danilo Krummrich <dakr@kernel.org>
Subject: Re: [PATCH v3 08/16] i2c: Let i2c-core.h include <linux/i2c.h>
Date: Mon, 29 Jun 2026 12:09:20 +0200 [thread overview]
Message-ID: <akJCr-OtGhoaR0vI@monoceros> (raw)
In-Reply-To: <akIRVj94lmCasfEF@ninjato>
[-- Attachment #1: Type: text/plain, Size: 1340 bytes --]
Hallo Wolfram,
On Mon, Jun 29, 2026 at 08:31:50AM +0200, Wolfram Sang wrote:
> On Sun, Jun 28, 2026 at 11:58:43PM +0200, Uwe Kleine-König (The Capable Hub) wrote:
> > The subsystem private header i2c-core.h uses several symbols defined in
> > <linux/i2c.h>, e.g. struct i2c_board_info and i2c_lock_bus()). This
> > doesn't pose a problem in practise because all files including
> > "i2c-core.h" also include <linux/i2c.h>.
> >
> > To make this more robust add an include statement for <linux/i2c.h>
> > making the header self-contained.
> >
> > Acked-by: Danilo Krummrich <dakr@kernel.org>
> > Signed-off-by: Uwe Kleine-König (The Capable Hub) <u.kleine-koenig@baylibre.com>
>
> Reviewed-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
>
> This shall go upstream with the rest of the series, right?
Yes, that's the plan. Linus didn't explicitly say he's happy with
merging this for -rc2, but he also didn't contradict, so I assume that
is what will happen.
For bisectability it isn't needed to let these go all together, but
given that the first patch touches <linux/mod_devicetable.h> which is an
intrusive change resulting in the need to rebuild nearly the complete
tree when pulled in, do the intrusive follow up changes in the same go
to only trigger the needed rebuild once.
Best regards
Uwe
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2026-06-29 10:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-28 21:58 [PATCH v3 00/16] mod_devicetable.h: Split into per subsystem headers Uwe Kleine-König (The Capable Hub)
2026-06-28 21:58 ` [PATCH v3 08/16] i2c: Let i2c-core.h include <linux/i2c.h> Uwe Kleine-König (The Capable Hub)
2026-06-29 6:31 ` Wolfram Sang
2026-06-29 10:09 ` Uwe Kleine-König (The Capable Hub) [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=akJCr-OtGhoaR0vI@monoceros \
--to=u.kleine-koenig@baylibre.com \
--cc=andi.shyti@kernel.org \
--cc=dakr@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox