public inbox for linux-kernel@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,
	Peter Rosin <peda@axentia.se>,
	Bartosz Golaszewski <brgl@bgdev.pl>
Subject: [PULL REQUEST] i2c-for-6.1-rc1-batch2
Date: Sun, 9 Oct 2022 20:13:35 +0200	[thread overview]
Message-ID: <Y0MPT6Mso6cD0mfN@shikoro> (raw)

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

The following changes since commit 2bca25eaeba6190efbfcb38ed169bd7ee43b5aaf:

  Merge tag 'spi-v6.1' of git://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi (2022-10-04 19:36:53 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux.git tags/i2c-for-6.1-rc1-batch2

for you to fetch changes up to fd66bd74afe880de4f008f96a795fedee887ff44:

  i2c: aspeed: Assert NAK when slave is busy (2022-10-05 21:06:46 +0200)

----------------------------------------------------------------
- correct a variable type in the new pci1xxxx driver
- add a new SoC to the qcom-cci driver
- fix an issue with the designware driver which now got enough testing
- the aspeed driver handles now busy target backends better

----------------------------------------------------------------
Colin Ian King (1):
      i2c: microchip: pci1xxxx: Fix comparison of -EPERM against an unsigned variable

Jarkko Nikula (1):
      i2c: designware: Fix handling of real but unexpected device interrupts

Matti Lehtimäki (2):
      dt-bindings: i2c: qcom,i2c-cci: Document MSM8226 compatible
      dt-bindings: i2c: qcom,i2c-cci: Document clocks for MSM8974

Quan Nguyen (1):
      i2c: aspeed: Assert NAK when slave is busy

Rayyan Ansari (1):
      i2c: qcom-cci: Add MSM8226 compatible


with much appreciated quality assurance from
----------------------------------------------------------------
Andy Shevchenko (1):
      (Rev.) i2c: designware: Fix handling of real but unexpected device interrupts

Krzysztof Kozlowski (2):
      (Rev.) dt-bindings: i2c: qcom,i2c-cci: Document clocks for MSM8974
      (Rev.) dt-bindings: i2c: qcom,i2c-cci: Document MSM8226 compatible

Loic Poulain (1):
      (Rev.) i2c: qcom-cci: Add MSM8226 compatible

 .../devicetree/bindings/i2c/qcom,i2c-cci.yaml      | 23 ++++++++++++++++++++--
 drivers/i2c/busses/i2c-aspeed.c                    |  9 ++++++++-
 drivers/i2c/busses/i2c-designware-core.h           |  7 +++++--
 drivers/i2c/busses/i2c-designware-master.c         | 13 ++++++++++++
 drivers/i2c/busses/i2c-mchp-pci1xxxx.c             |  2 +-
 drivers/i2c/busses/i2c-qcom-cci.c                  |  1 +
 6 files changed, 49 insertions(+), 6 deletions(-)

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

             reply	other threads:[~2022-10-09 18:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-09 18:13 Wolfram Sang [this message]
2022-10-11 18:22 ` [PULL REQUEST] i2c-for-6.1-rc1-batch2 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=Y0MPT6Mso6cD0mfN@shikoro \
    --to=wsa@kernel.org \
    --cc=brgl@bgdev.pl \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peda@axentia.se \
    --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