public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
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.17-rc3
Date: Sun, 24 Aug 2025 12:36:42 +0200	[thread overview]
Message-ID: <aKrrOlgY5fXBEG9U@shikoro> (raw)

[-- Attachment #1: Type: text/plain, Size: 2244 bytes --]

The following changes since commit c17b750b3ad9f45f2b6f7e6f7f4679844244f0b9:

  Linux 6.17-rc2 (2025-08-17 15:22:10 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux.git tags/i2c-for-6.17-rc3

for you to fetch changes up to 3dd22078026c7cad4d4a3f32c5dc5452c7180de8:

  Merge tag 'i2c-host-fixes-6.17-rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/andi.shyti/linux into i2c/for-current (2025-08-23 07:57:28 +0200)

----------------------------------------------------------------
i2c-for-6.17-rc3

- hisi: update maintainership
- rtl9300: fix several issues in xfer
  - check message length boundaries
  - correct multi-byte value composition on write
  - increase polling timeout
  - fix block transfer protocol

----------------------------------------------------------------
Alex Guo (1):
      i2c: rtl9300: Fix out-of-bounds bug in rtl9300_i2c_smbus_xfer

Devyn Liu (1):
      MAINTAINERS: i2c: Update i2c_hisi entry

Harshal Gohel (1):
      i2c: rtl9300: Fix multi-byte I2C write

Sven Eckelmann (2):
      i2c: rtl9300: Increase timeout for transfer polling
      i2c: rtl9300: Add missing count byte for SMBus Block Ops

Wolfram Sang (1):
      Merge tag 'i2c-host-fixes-6.17-rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/andi.shyti/linux into i2c/for-current


with much appreciated quality assurance from
----------------------------------------------------------------
Chris Packham (8):
      (Rev.) i2c: rtl9300: Add missing count byte for SMBus Block Ops
      (Test) i2c: rtl9300: Add missing count byte for SMBus Block Ops
      (Rev.) i2c: rtl9300: Increase timeout for transfer polling
      (Test) i2c: rtl9300: Increase timeout for transfer polling
      (Rev.) i2c: rtl9300: Fix multi-byte I2C write
      (Test) i2c: rtl9300: Fix multi-byte I2C write
      (Rev.) i2c: rtl9300: Fix out-of-bounds bug in rtl9300_i2c_smbus_xfer
      (Test) i2c: rtl9300: Fix out-of-bounds bug in rtl9300_i2c_smbus_xfer

Wolfram Sang (1):
      (Rev.) i2c: rtl9300: Fix out-of-bounds bug in rtl9300_i2c_smbus_xfer

 MAINTAINERS                      |  2 +-
 drivers/i2c/busses/i2c-rtl9300.c | 20 ++++++++++++--------
 2 files changed, 13 insertions(+), 9 deletions(-)

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

             reply	other threads:[~2025-08-24 10:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-24 10:36 Wolfram Sang [this message]
2025-08-24 14:34 ` [PULL REQUEST] i2c-for-6.17-rc3 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=aKrrOlgY5fXBEG9U@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