From: Andi Shyti <andi.shyti@kernel.org>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
linux-i2c <linux-i2c@vger.kernel.org>,
Andi Shyti <andi.shyti@kernel.org>
Subject: i2c-host-fixes for v6.19-rc9
Date: Sat, 7 Feb 2026 00:57:06 +0100 [thread overview]
Message-ID: <aYZ-AZcfwfG1poEH@zenone.zhora.eu> (raw)
Hi Wolfram,
here is the fixes pull request. After you cherry-picked from my
previous pull request, I reset my -fixes branch on top of your
for-current branch, so this should be an easy merge.
This pull request contains just one fix from Carlos for
mx-lpi2c.
I have already sent the merge window pull request and that is
still valid. I am collecting additional patches in i2c-host-2 for
next week. All patches in that branch are tested as usual in my
-next branch.
I wish you a great weekend!
Andi
The following changes since commit b126097b0327437048bd045a0e4d273dea2910dd:
i2c: imx: preserve error state in block data length handler (2026-02-03 21:47:48 +0100)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/andi.shyti/linux.git tags/i2c-host-fixes-6.19-rc9
for you to fetch changes up to b4b4d88ebfbfd3aadb4c9a0f2bfe1abdbaf5822c:
i2c: imx-lpi2c: fix SMBus block read NACK after byte count (2026-02-04 02:52:16 +0100)
----------------------------------------------------------------
i2c-host-fixes for v6.19-rc9
imx-lpi2c: fix premature NACK in SMBus block read handling
----------------------------------------------------------------
Carlos Song (1):
i2c: imx-lpi2c: fix SMBus block read NACK after byte count
drivers/i2c/busses/i2c-imx-lpi2c.c | 107 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++------------------------
1 file changed, 83 insertions(+), 24 deletions(-)
next reply other threads:[~2026-02-06 23:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-06 23:57 Andi Shyti [this message]
2026-02-08 17:16 ` i2c-host-fixes for v6.19-rc9 Wolfram Sang
2026-02-10 11:30 ` Andi Shyti
2026-02-10 11:40 ` Wolfram Sang
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=aYZ-AZcfwfG1poEH@zenone.zhora.eu \
--to=andi.shyti@kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wsa+renesas@sang-engineering.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.