From: "Uwe Kleine-König (The Capable Hub)" <u.kleine-koenig@baylibre.com>
To: MyungJoo Ham <myungjoo.ham@samsung.com>,
Chanwoo Choi <cw00.choi@samsung.com>
Cc: linux-kernel@vger.kernel.org, Krzysztof Kozlowski <krzk@kernel.org>
Subject: Re: [PATCH v1 0/2] extcon: Rework initialization of i2c_device_id
Date: Tue, 17 Nov 2026 15:53:15 +0100 [thread overview]
Message-ID: <avxptCL2mq7Z3vPi@monoceros> (raw)
In-Reply-To: <aloDsjYyv3gCsx39@monoceros>
[-- Attachment #1: Type: text/plain, Size: 1509 bytes --]
Hello,
On Fri, Jul 17, 2026 at 12:31:20PM +0200, Uwe Kleine-König (The Capable Hub) wrote:
> On Wed, Jun 10, 2026 at 07:10:51PM +0200, Uwe Kleine-König (The Capable Hub) wrote:
> > On Mon, May 18, 2026 at 12:41:43PM +0200, Uwe Kleine-König (The Capable Hub) wrote:
> > > Hello,
> > >
> > > I plan to do the following to the definition of i2c_device_id:
> > >
> > > diff --git a/include/linux/mod_devicetable.h b/include/linux/mod_devicetable.h
> > > index 23ff24080dfd..aebd3a5e90af 100644
> > > --- a/include/linux/mod_devicetable.h
> > > +++ b/include/linux/mod_devicetable.h
> > > @@ -477,7 +477,11 @@ struct rpmsg_device_id {
> > >
> > > struct i2c_device_id {
> > > char name[I2C_NAME_SIZE];
> > > - kernel_ulong_t driver_data; /* Data private to the driver */
> > > + union {
> > > + /* Data private to the driver */
> > > + kernel_ulong_t driver_data;
> > > + const void *driver_data_ptr;
> > > + };
> > > };
> > >
> > > /* pci_epf */
> >
> > I want to work on that, but I'd need this patch series to be in for it.
> > Do you still have this patch on your radar?
>
> While I still have to make several patches land before I can modify
> struct i2c_device_id, getting the patches from this thread in would at
> least make my queue smaller.
>
> FTR: The series still applies fine to next-20260716.
It's November and the series still applies to next-20261116. Does
someone still have this patch set on their radar?
Best regards
Uwe
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2026-11-17 14:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-18 10:41 [PATCH v1 0/2] extcon: Rework initialization of i2c_device_id Uwe Kleine-König (The Capable Hub)
2026-05-18 10:41 ` [PATCH v1 1/2] extcon: rt8973: Drop unused driver data Uwe Kleine-König (The Capable Hub)
2026-05-18 10:41 ` [PATCH v1 2/2] extcon: Use named initializers for arrays of i2c_device_data Uwe Kleine-König (The Capable Hub)
2026-06-10 17:10 ` [PATCH v1 0/2] extcon: Rework initialization of i2c_device_id Uwe Kleine-König (The Capable Hub)
2026-07-17 10:31 ` Uwe Kleine-König (The Capable Hub)
2026-11-17 14:53 ` 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=avxptCL2mq7Z3vPi@monoceros \
--to=u.kleine-koenig@baylibre.com \
--cc=cw00.choi@samsung.com \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=myungjoo.ham@samsung.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.