[GIT PULL] i2c fixes for v7.2-rc4

Andi Shyti <[email protected]>
Newsgroups org.kernel.vger.linux-i2c,org.kernel.vger.linux-kernel
Message-ID <[email protected]>
Hi Linus,

here is the fixes pull request for v7.2-rc4.

It contains a handful of small fixes for host controller drivers.

One patch also adds Wolfram Sang to CREDITS after more than a
decade of work on I2C.

Thanks,
Andi

The following changes since commit a13c140cc289c0b7b3770bce5b3ad42ab35074aa:

  Linux 7.2-rc3 (2026-07-12 14:16:39 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/andi.shyti/linux.git tags/i2c-fixes-7.2-rc4

for you to fetch changes up to deb35336b5bfed5db9231b5348bc1514db930797:

  i2c: mediatek: fix WRRD for SoCs without auto_restart option (2026-07-15 00:21:51 +0200)

----------------------------------------------------------------
i2c-fixes for v7.2-rc4

imx: fix empty SMBus block reads in atomic and IRQ paths
spacemit: return IRQ_NONE for empty interrupt status
mlxbf: fix a use-after-free issue
mediatek: restore WRRD support without automatic restart
CREDITS: add Wolfram Sang

----------------------------------------------------------------
Andi Shyti (1):
      CREDITS: Add Wolfram Sang

Pei Xiao (1):
      i2c: spacemit: fix spurious IRQ handling returning IRQ_HANDLED

Roman Vivchar (1):
      i2c: mediatek: fix WRRD for SoCs without auto_restart option

Vincent Jardin (2):
      i2c: imx: fix locked bus on SMBus block-read of 0 (atomic)
      i2c: imx: fix locked bus on SMBus block-read of 0 (IRQ)

Xuanqiang Luo (1):
      i2c: mlxbf: Fix use-after-free in mlxbf_i2c_init_resource()

 CREDITS                         |  7 +++++++
 drivers/i2c/busses/i2c-imx.c    | 36 +++++++++++++++++++++++++++++++++---
 drivers/i2c/busses/i2c-k1.c     |  2 +-
 drivers/i2c/busses/i2c-mlxbf.c  |  4 +++-
 drivers/i2c/busses/i2c-mt65xx.c |  2 +-
 5 files changed, 45 insertions(+), 6 deletions(-)
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.