From: Andi Shyti <andi.shyti@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: lkml <linux-kernel@vger.kernel.org>,
linux-i2c <linux-i2c@vger.kernel.org>,
Andi Shyti <andi.shyti@kernel.org>
Subject: [GIT PULL] i2c fixes for v7.3-rc6
Date: Sun, 4 Oct 2026 12:35:20 +0200 [thread overview]
Message-ID: <asIofz6JIxKb2s-X@zenone.zhora.eu> (raw)
Hi Linus,
here is the I2C fixes pull request for v7.3-rc6.
Three xiic patches fix block reads, plus one small at91 error
path cleanup following up on a fix from a previous pull request.
Thanks and perhaps see you in Prague :-)
Andi
The following changes since commit 72d3fcf802c45d00b300f25b848a93c3a2bd7c7e:
Linux 7.3-rc5 (2026-09-27 13:55:01 -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.3-rc6
for you to fetch changes up to c98bf3b86609a18ab16d067280257326e557c636:
i2c: at91: release DMA channels when probe defers (2026-10-01 13:51:54 +0200)
----------------------------------------------------------------
i2c-fixes for v7.3-rc6
Three patches in xiic for fixing the block reads and a single
cleanup in the error path.
- at91: also release DMA channels when deferring probe
- xiic: fix SMBus block reads with PEC
----------------------------------------------------------------
Abdurrahman Hussain (3):
i2c: xiic: preserve PEC byte length in SMBus block read setup
i2c: xiic: defer RX_FULL until all trailing bytes are in FIFO
i2c: xiic: don't clobber msg->len to signal block-read completion
Hongjian Dai (1):
i2c: at91: release DMA channels when probe defers
drivers/i2c/busses/i2c-at91-master.c | 8 +++++++-
drivers/i2c/busses/i2c-xiic.c | 61 ++++++++++++++++++++++++++++++++++++++++++++++---------------
2 files changed, 53 insertions(+), 16 deletions(-)
next reply other threads:[~2026-10-04 10:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-04 10:35 Andi Shyti [this message]
2026-10-04 16:50 ` 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=asIofz6JIxKb2s-X@zenone.zhora.eu \
--to=andi.shyti@kernel.org \
--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
all inboxes | Powered by JetHome®