From: "Uwe Kleine-König (The Capable Hub)" <u.kleine-koenig@baylibre.com>
To: Mika Westerberg <mika.westerberg@linux.intel.com>,
Andi Shyti <andi.shyti@kernel.org>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Jan Dabros <jsd@semihalf.com>,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/2] i2c: Consistently define pci_device_ids using named initializers
Date: Fri, 22 May 2026 22:35:12 +0200 [thread overview]
Message-ID: <cover.1779481436.git.u.kleine-koenig@baylibre.com> (raw)
Hello,
Changes since (implicit) v1 (available at
https://lore.kernel.org/all/20260504142639.2119645-2-u.kleine-koenig@baylibre.com/
):
- split by driver (requested by Andy)
Andy also suggested to use PCI_DEVICE_DATA() in the designware driver. I didn't
implement that, because I think its advantages don't outweight its downsides.
We two already discussed that in other threads where I sent similar patches and
didn't find a compromise. I think
https://lore.kernel.org/all/af7yKdRdDSJjkoIk@monoceros/ is the most detailed
discussion if you want to read about our arguments.
Best regards
Uwe
Uwe Kleine-König (The Capable Hub) (2):
i2c: designware-pcidrv: Consistently define pci_device_ids using named
initializers
i2c: eg20t: Consistently define pci_device_ids using named
initializers
drivers/i2c/busses/i2c-designware-pcidrv.c | 78 +++++++++++-----------
drivers/i2c/busses/i2c-eg20t.c | 10 +--
2 files changed, 44 insertions(+), 44 deletions(-)
base-commit: 254f49634ee16a731174d2ae34bc50bd5f45e731
--
2.47.3
next reply other threads:[~2026-05-22 20:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-22 20:35 Uwe Kleine-König (The Capable Hub) [this message]
2026-05-22 20:35 ` [PATCH v2 1/2] i2c: designware-pcidrv: Consistently define pci_device_ids using named initializers Uwe Kleine-König (The Capable Hub)
2026-05-25 4:44 ` Mika Westerberg
2026-05-22 20:35 ` [PATCH v2 2/2] i2c: eg20t: " Uwe Kleine-König (The Capable Hub)
2026-06-09 8:11 ` [PATCH v2 0/2] i2c: " Andi Shyti
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=cover.1779481436.git.u.kleine-koenig@baylibre.com \
--to=u.kleine-koenig@baylibre.com \
--cc=andi.shyti@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=jsd@semihalf.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.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