From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Sven Eckelmann <sven@narfation.org>
Cc: Jonas Jelonek <jelonek.jonas@gmail.com>,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
Harshal Gohel <hg@simonwunderlich.de>,
Simon Wunderlich <sw@simonwunderlich.de>,
Andi Shyti <andi.shyti@kernel.org>,
Chris Packham <chris.packham@alliedtelesis.co.nz>
Subject: Re: [PATCH i2c-host v6] i2c: rtl9300: Implement I2C block read and write
Date: Fri, 26 Sep 2025 10:36:46 +0200 [thread overview]
Message-ID: <aNZQnlUML0jIhXIM@shikoro> (raw)
In-Reply-To: <1838669.VLH7GnMWUR@ripper>
[-- Attachment #1: Type: text/plain, Size: 663 bytes --]
On Fri, Sep 26, 2025 at 10:34:40AM +0200, Sven Eckelmann wrote:
> On Friday, 26 September 2025 10:16:19 CEST Jonas Jelonek wrote:
> > Thanks for taking care of this quickly.
> > Maybe we should include another patch here which fixes the committed version
> > of my patch, i.e. removing I2C_FUNC_SMBUS_I2C_BLOCK, with CC to stable. Since
> > the patch was also merged to stable, it is somewhat broken there now.
>
> Yes, sounds good. Will submit it [1] tomorrow after the ~24h dwell time (if no
> one else requests anything different).
I am getting a little confused already, so please make sure I know which
patches to apply where in what order.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2025-09-26 8:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-26 7:52 [PATCH i2c-host v6] i2c: rtl9300: Implement I2C block read and write Sven Eckelmann
2025-09-26 8:16 ` Jonas Jelonek
2025-09-26 8:34 ` Sven Eckelmann
2025-09-26 8:36 ` Wolfram Sang [this message]
2025-09-27 9:55 ` Sven Eckelmann
2025-09-27 10:23 ` Jonas Jelonek
2025-09-27 22:33 ` 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=aNZQnlUML0jIhXIM@shikoro \
--to=wsa+renesas@sang-engineering.com \
--cc=andi.shyti@kernel.org \
--cc=chris.packham@alliedtelesis.co.nz \
--cc=hg@simonwunderlich.de \
--cc=jelonek.jonas@gmail.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sven@narfation.org \
--cc=sw@simonwunderlich.de \
/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.