From: Wolfram Sang <wsa@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
Bartosz Golaszewski <brgl@bgdev.pl>,
Andi Shyti <andi.shyti@kernel.org>
Subject: [PULL REQUEST] i2c-for-6.16-rc4
Date: Sat, 28 Jun 2025 21:03:34 +0200 [thread overview]
Message-ID: <aGA8hmxiZJcIIqOI@shikoro> (raw)
[-- Attachment #1: Type: text/plain, Size: 2663 bytes --]
The following changes since commit 86731a2a651e58953fc949573895f2fa6d456841:
Linux 6.16-rc3 (2025-06-22 13:30:08 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux.git tags/i2c-for-6.16-rc4
for you to fetch changes up to f40213cd93e608ee78b5e25db042c42ec07139fe:
i2c: scx200_acb: depends on HAS_IOPORT (2025-06-27 12:28:33 +0200)
----------------------------------------------------------------
i2c-for-6.16-rc4
- imx: fix SMBus protocol compliance during block read
- omap: fix error handling path in probe
- robotfuzz, tiny-usb: prevent zero-length reads
- x86, designware, amdisp: fix build error when modules are
disabled (agreed to go in via i2c)
- scx200_acb: fix build error because of missing HAS_IOPORT
----------------------------------------------------------------
Christophe JAILLET (1):
i2c: omap: Fix an error handling path in omap_i2c_probe()
Johannes Berg (1):
i2c: scx200_acb: depends on HAS_IOPORT
Lukasz Kucharczyk (1):
i2c: imx: fix emulated smbus block read
Pratap Nirujogi (3):
i2c: designware: Initialize adapter name only when not set
i2c: amd-isp: Initialize unique adapter name
platform/x86: Use i2c adapter name to fix build errors
Wolfram Sang (3):
i2c: robotfuzz-osif: disable zero-length read messages
i2c: tiny-usb: disable zero-length read messages
Merge tag 'i2c-host-fixes-6.16-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/andi.shyti/linux into i2c/for-current
with much appreciated quality assurance from
----------------------------------------------------------------
Carlos Song (1):
(Rev.) i2c: imx: fix emulated smbus block read
Randy Dunlap (3):
(Test) platform/x86: Use i2c adapter name to fix build errors
(Test) i2c: amd-isp: Initialize unique adapter name
(Test) i2c: designware: Initialize adapter name only when not set
Stefan Eichenberger (1):
(Rev.) i2c: imx: fix emulated smbus block read
MAINTAINERS | 1 +
drivers/i2c/busses/Kconfig | 2 +-
drivers/i2c/busses/i2c-designware-amdisp.c | 2 ++
drivers/i2c/busses/i2c-designware-master.c | 5 +++--
drivers/i2c/busses/i2c-imx.c | 3 ++-
drivers/i2c/busses/i2c-omap.c | 7 +++++--
drivers/i2c/busses/i2c-robotfuzz-osif.c | 6 ++++++
drivers/i2c/busses/i2c-tiny-usb.c | 6 ++++++
drivers/platform/x86/amd/amd_isp4.c | 3 ++-
include/linux/soc/amd/isp4_misc.h | 12 ++++++++++++
10 files changed, 40 insertions(+), 7 deletions(-)
create mode 100644 include/linux/soc/amd/isp4_misc.h
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2025-06-28 19:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-28 19:03 Wolfram Sang [this message]
2025-06-28 22:33 ` [PULL REQUEST] i2c-for-6.16-rc4 pr-tracker-bot
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=aGA8hmxiZJcIIqOI@shikoro \
--to=wsa@kernel.org \
--cc=andi.shyti@kernel.org \
--cc=brgl@bgdev.pl \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).