From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Andi Shyti <andi.shyti@kernel.org>
Cc: linux-i2c@vger.kernel.org
Subject: [PULL REQUEST?] i2c/for-andi for v7.2
Date: Mon, 8 Jun 2026 22:32:42 +0200 [thread overview]
Message-ID: <aicm6trmpoPZpT8v@shikoro> (raw)
[-- Attachment #1: Type: text/plain, Size: 2377 bytes --]
Hi Andi,
I don't know if you want to pull this branch or pick the patches
individually. Anyhow, I want to let you know that here are some patches
I already reviewed. I think they are good to go for v7.2.
Happy hacking,
Wolfram
The following changes since commit 5200f5f493f79f14bbdc349e402a40dfb32f23c8:
Linux 7.1-rc4 (2026-05-17 13:59:58 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux.git i2c/for-andi
for you to fetch changes up to 583c45839cb343db171f5c5e40850d6eb906e949:
dt-bindings: i2c: qcom-cci: Document Glymur compatible (2026-05-30 16:07:49 +0200)
----------------------------------------------------------------
Abdurrahman Hussain (1):
i2c: mux: reg: use device property accessors
Andy Shevchenko (1):
i2c: acpi: Return -ENOENT when no resources found in i2c_acpi_client_count()
Herve Codina (1):
i2c: at91: Add MCHP_LAN966X_PCI dependency
Nihal Kumar Gupta (2):
dt-bindings: i2c: qcom-cci: Document Shikra compatible
dt-bindings: i2c: qcom-cci: Document Glymur compatible
Uwe Kleine-König (The Capable Hub) (1):
i2c: Use named initializers for arrays of i2c_device_data
with much appreciated quality assurance from
----------------------------------------------------------------
Bryan O'Donoghue (1):
(Rev.) dt-bindings: i2c: qcom-cci: Document Shikra compatible
Documentation/devicetree/bindings/i2c/qcom,i2c-cci.yaml | 4 ++++
drivers/i2c/busses/Kconfig | 2 +-
drivers/i2c/i2c-core-acpi.c | 7 +++++--
drivers/i2c/i2c-core-base.c | 4 ++--
drivers/i2c/i2c-slave-eeprom.c | 16 ++++++++--------
drivers/i2c/i2c-slave-testunit.c | 2 +-
drivers/i2c/i2c-smbus.c | 2 +-
drivers/i2c/muxes/i2c-mux-ltc4306.c | 4 ++--
drivers/i2c/muxes/i2c-mux-pca9541.c | 4 ++--
drivers/i2c/muxes/i2c-mux-pca954x.c | 36 ++++++++++++++++++------------------
drivers/i2c/muxes/i2c-mux-reg.c | 90 ++++++++++++++++++++++++++++++++++++++----------------------------------------------------
11 files changed, 82 insertions(+), 89 deletions(-)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2026-06-08 20:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-08 20:32 Wolfram Sang [this message]
2026-06-09 11:15 ` [PULL REQUEST?] i2c/for-andi for v7.2 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=aicm6trmpoPZpT8v@shikoro \
--to=wsa+renesas@sang-engineering.com \
--cc=andi.shyti@kernel.org \
--cc=linux-i2c@vger.kernel.org \
/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