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.16-rc3
Date: Sun, 22 Jun 2025 15:20:28 +0200	[thread overview]
Message-ID: <aFgDHBHwY5ElWILx@shikoro> (raw)

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

The following changes since commit 19272b37aa4f83ca52bdf9c16d5d81bdd1354494:

  Linux 6.16-rc1 (2025-06-08 13:44:43 -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-rc3

for you to fetch changes up to a6c23dac756b9541b33aa3bcd30f464df2879209:

  i2c: k1: check for transfer error (2025-06-21 22:17:02 +0200)

----------------------------------------------------------------
i2c-for-6.16-rc3

- subsystem: convert drivers to use recent callbacks of struct i2c_algorithm
  A typical after-rc1 cleanup, which I couldn't send in time for rc2
- tegra: fix YAML conversion of device tree bindings
- k1: re-add a check which got lost during upstreaming

----------------------------------------------------------------
Akhil R (1):
      dt-bindings: i2c: nvidia,tegra20-i2c: Specify the required properties

Alex Elder (1):
      i2c: k1: check for transfer error

Wolfram Sang (2):
      i2c: use inclusive callbacks in struct i2c_algorithm
      Merge tag 'i2c-host-fixes-6.16-rc2' of git://git.kernel.org/pub/scm/linux/kernel/git/andi.shyti/linux into i2c/for-current


with much appreciated quality assurance from
----------------------------------------------------------------
Krzysztof Kozlowski (1):
      (Rev.) dt-bindings: i2c: nvidia,tegra20-i2c: Specify the required properties

Troy Mitchell (1):
      (Rev.) i2c: k1: check for transfer error

 .../bindings/i2c/nvidia,tegra20-i2c.yaml           | 24 +++++++++++++++++++++-
 drivers/i2c/algos/i2c-algo-bit.c                   |  4 ++--
 drivers/i2c/algos/i2c-algo-pca.c                   |  4 ++--
 drivers/i2c/algos/i2c-algo-pcf.c                   |  4 ++--
 drivers/i2c/busses/i2c-amd-mp2-plat.c              |  2 +-
 drivers/i2c/busses/i2c-aspeed.c                    |  8 ++++----
 drivers/i2c/busses/i2c-at91-master.c               |  4 ++--
 drivers/i2c/busses/i2c-axxia.c                     |  2 +-
 drivers/i2c/busses/i2c-bcm-iproc.c                 |  2 +-
 drivers/i2c/busses/i2c-cadence.c                   | 10 ++++-----
 drivers/i2c/busses/i2c-cgbc.c                      |  4 ++--
 drivers/i2c/busses/i2c-eg20t.c                     |  2 +-
 drivers/i2c/busses/i2c-emev2.c                     |  6 +++---
 drivers/i2c/busses/i2c-exynos5.c                   |  6 +++---
 drivers/i2c/busses/i2c-gxp.c                       |  6 +++---
 drivers/i2c/busses/i2c-img-scb.c                   |  2 +-
 drivers/i2c/busses/i2c-imx-lpi2c.c                 |  8 ++++----
 drivers/i2c/busses/i2c-imx.c                       |  8 ++++----
 drivers/i2c/busses/i2c-k1.c                        |  2 +-
 drivers/i2c/busses/i2c-keba.c                      |  2 +-
 drivers/i2c/busses/i2c-mchp-pci1xxxx.c             |  2 +-
 drivers/i2c/busses/i2c-meson.c                     |  4 ++--
 drivers/i2c/busses/i2c-microchip-corei2c.c         |  2 +-
 drivers/i2c/busses/i2c-mt65xx.c                    |  2 +-
 drivers/i2c/busses/i2c-mxs.c                       |  2 +-
 drivers/i2c/busses/i2c-nomadik.c                   |  4 ++--
 drivers/i2c/busses/i2c-npcm7xx.c                   |  6 +++---
 drivers/i2c/busses/i2c-omap.c                      |  6 +++---
 drivers/i2c/busses/i2c-pnx.c                       |  2 +-
 drivers/i2c/busses/i2c-pxa.c                       | 16 +++++++--------
 drivers/i2c/busses/i2c-qcom-cci.c                  |  4 ++--
 drivers/i2c/busses/i2c-qcom-geni.c                 |  4 ++--
 drivers/i2c/busses/i2c-qup.c                       |  8 ++++----
 drivers/i2c/busses/i2c-rcar.c                      | 10 ++++-----
 drivers/i2c/busses/i2c-s3c2410.c                   |  6 +++---
 drivers/i2c/busses/i2c-sh7760.c                    |  4 ++--
 drivers/i2c/busses/i2c-sh_mobile.c                 |  4 ++--
 drivers/i2c/busses/i2c-stm32f7.c                   |  4 ++--
 drivers/i2c/busses/i2c-synquacer.c                 |  4 ++--
 drivers/i2c/busses/i2c-tegra.c                     |  6 +++---
 drivers/i2c/busses/i2c-xiic.c                      |  4 ++--
 drivers/i2c/busses/i2c-xlp9xx.c                    |  2 +-
 drivers/i2c/i2c-atr.c                              |  2 +-
 drivers/i2c/i2c-mux.c                              |  6 +++---
 drivers/i2c/muxes/i2c-demux-pinctrl.c              |  4 ++--
 45 files changed, 125 insertions(+), 103 deletions(-)

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

             reply	other threads:[~2025-06-22 13:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-22 13:20 Wolfram Sang [this message]
2025-06-22 18:00 ` [PULL REQUEST] i2c-for-6.16-rc3 Linus Torvalds
2025-06-25  9:25   ` Wolfram Sang
2025-06-25 15:52     ` Linus Torvalds
2025-06-22 19:55 ` 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=aFgDHBHwY5ElWILx@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