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-rc5
Date: Sun, 7 Sep 2025 12:57:04 +0200	[thread overview]
Message-ID: <aL1lACUHl9td3dtH@shikoro> (raw)

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

The following changes since commit b320789d6883cc00ac78ce83bccbfe7ed58afcf0:

  Linux 6.17-rc4 (2025-08-31 15:33:07 -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-rc5

for you to fetch changes up to d035b4baebfc5112b128b66cafd45d2522a9c8f1:

  Merge tag 'i2c-host-fixes-6.17-rc5' of git://git.kernel.org/pub/scm/linux/kernel/git/andi.shyti/linux into i2c/for-current (2025-09-06 10:17:35 +0200)

----------------------------------------------------------------
i2c-for-6.17-rc5

- i801: drop superfluous WDT entry for Birch
- rtl9300:
  - fix channel number check in probe
  - check data length boundaries in xfer
  - drop broken SMBus quick operation

----------------------------------------------------------------
Chiasheng Lee (1):
      i2c: i801: Hide Intel Birch Stream SoC TCO WDT

Jonas Jelonek (3):
      i2c: rtl9300: fix channel number bound check
      i2c: rtl9300: ensure data length is within supported range
      i2c: rtl9300: remove broken SMBus Quick operation support

Wolfram Sang (1):
      Merge tag 'i2c-host-fixes-6.17-rc5' 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 (6):
      (Rev.) i2c: rtl9300: remove broken SMBus Quick operation support
      (Test) i2c: rtl9300: remove broken SMBus Quick operation support
      (Rev.) i2c: rtl9300: ensure data length is within supported range
      (Test) i2c: rtl9300: ensure data length is within supported range
      (Rev.) i2c: rtl9300: fix channel number bound check
      (Test) i2c: rtl9300: fix channel number bound check

Jarkko Nikula (1):
      (Rev.) i2c: i801: Hide Intel Birch Stream SoC TCO WDT

Markus Stockhausen (3):
      (Test) i2c: rtl9300: remove broken SMBus Quick operation support
      (Test) i2c: rtl9300: ensure data length is within supported range
      (Test) i2c: rtl9300: fix channel number bound check

Mika Westerberg (1):
      (Rev.) i2c: i801: Hide Intel Birch Stream SoC TCO WDT

Sven Eckelmann (3):
      (Test) i2c: rtl9300: remove broken SMBus Quick operation support
      (Test) i2c: rtl9300: ensure data length is within supported range
      (Test) i2c: rtl9300: fix channel number bound check

 drivers/i2c/busses/i2c-i801.c    |  2 +-
 drivers/i2c/busses/i2c-rtl9300.c | 22 ++++++++--------------
 2 files changed, 9 insertions(+), 15 deletions(-)

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

             reply	other threads:[~2025-09-07 10:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-07 10:57 Wolfram Sang [this message]
2025-09-07 21:23 ` [PULL REQUEST] i2c-for-6.17-rc5 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=aL1lACUHl9td3dtH@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