From: Wolfram Sang <wsa+renesas@sang-engineering•com>
To: Bartosz Golaszewski <brgl@kernel•org>
Cc: "Bartosz Golaszewski" <bartosz.golaszewski@oss•qualcomm.com>,
"Andi Shyti" <andi.shyti@kernel•org>,
"Chen-Yu Tsai" <wens@kernel•org>,
"Jernej Skrabec" <jernej.skrabec@gmail•com>,
"Samuel Holland" <samuel@sholland•org>,
"Khalil Blaiech" <kblaiech@nvidia•com>,
"Asmaa Mnebhi" <asmaa@nvidia•com>,
"Jean Delvare" <jdelvare@suse•com>,
"Madhavan Srinivasan" <maddy@linux•ibm.com>,
"Michael Ellerman" <mpe@ellerman•id.au>,
"Nicholas Piggin" <npiggin@gmail•com>,
"Christophe Leroy (CS GROUP)" <chleroy@kernel•org>,
"Andreas Färber" <afaerber@suse•de>,
"Manivannan Sadhasivam" <mani@kernel•org>,
linux-i2c@vger•kernel.org, linux-kernel@vger•kernel.org,
linux-arm-kernel@lists•infradead.org,
linux-sunxi@lists•linux.dev, linuxppc-dev@lists•ozlabs.org,
linux-actions@lists•infradead.org
Subject: Re: [PATCH 00/12] i2c: add and start using i2c_adapter-specific printk helpers
Date: Wed, 14 Jan 2026 16:22:17 +0100 [thread overview]
Message-ID: <aWe0qYCOFNww_wSL@ninjato> (raw)
In-Reply-To: <CAMRc=MeDZf=J4L8M9QTAP+JXGNUFfs1_HyD3fbMOQ18AR29GYw@mail.gmail.com>
> FYI: I think the road-map will look something like this: v7.1 will get
> new interfaces and most controllers under drivers/i2c/ converted as
> this can be done within your tree exclusively. For v7.2 (with the new
> interfaces upstream) we can think about converting all i2c controller
> drivers treewide to the new helpers. Once v7.2-rc1 is tagged, I would
> try to remove struct device from struct i2c_adapter locally and send
> it to autobuilders for testing. If that goes well, we could create
> struct i2c_adapter_private or something like this and store its
> address in struct i2c_adapter. This new struct would be controlled by
> i2c core and contain struct device. With that out of the way, for v7.4
> we could think about adding SRCU into the mix (possibly using the
> then-available revocable).
>
> If all goes well, we should be done in early 2027. :)
With this plan, what could possibly go wrong? :)
prev parent reply other threads:[~2026-01-14 15:22 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-23 10:02 [PATCH 00/12] i2c: add and start using i2c_adapter-specific printk helpers Bartosz Golaszewski
2025-12-23 10:02 ` [PATCH 01/12] i2c: add " Bartosz Golaszewski
2025-12-25 18:30 ` kernel test robot
2025-12-25 19:33 ` kernel test robot
2025-12-23 10:02 ` [PATCH 02/12] i2c: sun6i-p2wi: use " Bartosz Golaszewski
2025-12-23 11:04 ` Chen-Yu Tsai
2025-12-23 10:02 ` [PATCH 03/12] i2c: mlxbf: " Bartosz Golaszewski
2025-12-23 10:02 ` [PATCH 04/12] i2c: isch: " Bartosz Golaszewski
2025-12-23 10:02 ` [PATCH 05/12] i2c: ali1535: " Bartosz Golaszewski
2025-12-23 10:02 ` [PATCH 06/12] i2c: scmi: " Bartosz Golaszewski
2025-12-23 10:02 ` [PATCH 07/12] i2c: ali15x3: " Bartosz Golaszewski
2025-12-23 10:02 ` [PATCH 08/12] i2c: powermac: " Bartosz Golaszewski
2025-12-23 10:02 ` [PATCH 09/12] i2c: owl: " Bartosz Golaszewski
2025-12-23 10:02 ` [PATCH 10/12] i2c: nforce2: " Bartosz Golaszewski
2025-12-23 10:02 ` [PATCH 11/12] i2c: amd756: " Bartosz Golaszewski
2025-12-23 10:02 ` [PATCH 12/12] i2c: piix4: " Bartosz Golaszewski
2025-12-23 14:23 ` [PATCH 00/12] i2c: add and start using " Johan Hovold
2025-12-23 15:11 ` Bartosz Golaszewski
2026-01-19 11:03 ` Johan Hovold
2026-01-19 11:17 ` Bartosz Golaszewski
2026-01-19 11:32 ` Johan Hovold
2026-01-13 10:03 ` Big I2C core changes coming up this year (was: " Wolfram Sang
2026-01-19 10:58 ` Johan Hovold
2026-01-13 10:44 ` Wolfram Sang
2026-01-13 10:59 ` Bartosz Golaszewski
2026-01-13 11:50 ` Wolfram Sang
2026-01-14 13:36 ` Bartosz Golaszewski
2026-01-14 15:22 ` Wolfram Sang [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=aWe0qYCOFNww_wSL@ninjato \
--to=wsa+renesas@sang-engineering$(echo .)com \
--cc=afaerber@suse$(echo .)de \
--cc=andi.shyti@kernel$(echo .)org \
--cc=asmaa@nvidia$(echo .)com \
--cc=bartosz.golaszewski@oss$(echo .)qualcomm.com \
--cc=brgl@kernel$(echo .)org \
--cc=chleroy@kernel$(echo .)org \
--cc=jdelvare@suse$(echo .)com \
--cc=jernej.skrabec@gmail$(echo .)com \
--cc=kblaiech@nvidia$(echo .)com \
--cc=linux-actions@lists$(echo .)infradead.org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-i2c@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-sunxi@lists$(echo .)linux.dev \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=maddy@linux$(echo .)ibm.com \
--cc=mani@kernel$(echo .)org \
--cc=mpe@ellerman$(echo .)id.au \
--cc=npiggin@gmail$(echo .)com \
--cc=samuel@sholland$(echo .)org \
--cc=wens@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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