From: Wolfram Sang <wsa@kernel.org>
To: Jean Delvare <jdelvare@suse.de>
Cc: Linux I2C <linux-i2c@vger.kernel.org>,
Crestez Dan Leonard <leonard.crestez@intel.com>
Subject: Re: [PATCH 0/7] Rework block read support among i2cget and i2cdump
Date: Sat, 26 Jun 2021 17:30:25 +0200 [thread overview]
Message-ID: <YNdIEUpBoToGN7JY@kunai> (raw)
In-Reply-To: <20210608172338.0cf520a1@endymion>
[-- Attachment #1: Type: text/plain, Size: 411 bytes --]
Hi Jean,
> The idea would be to get the first 6 patches in the upcoming i2c-tools
> v4.3, and apply the 7th patch "later" (either immediately after that
> release, or some time later, I'm not sure).
I agree with this approach.
I had a glimpse at the patches and think they look good so far. I would
have squashed patches 1+2, but this minor, of course. I'll try to test
them this weekend, too. Let's see...
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-06-26 15:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-08 15:23 [PATCH 0/7] Rework block read support among i2cget and i2cdump Jean Delvare
2021-06-08 15:28 ` [PATCH 1/7] i2cget: Add support for I2C block data Jean Delvare
2021-06-27 10:11 ` Wolfram Sang
2021-07-12 9:36 ` Jean Delvare
2021-06-08 15:29 ` [PATCH 2/7] i2cget: Document the support of I2C block reads Jean Delvare
2021-06-08 15:29 ` [PATCH 3/7] i2cget: Add support for SMBus block read Jean Delvare
2021-06-08 15:30 ` [PATCH 4/7] i2cdump: Remove dead code Jean Delvare
2021-06-08 15:30 ` [PATCH 5/7] i2cdump: Add range support with mode i (I2C block) Jean Delvare
2021-06-08 15:31 ` [PATCH 6/7] i2cdump: Deprecate SMBus block mode Jean Delvare
2021-06-08 15:32 ` [PATCH 7/7] i2cdump: Remove support for " Jean Delvare
2021-06-26 15:30 ` Wolfram Sang [this message]
2021-07-12 9:58 ` [PATCH 0/7] Rework block read support among i2cget and i2cdump Jean Delvare
2021-07-19 15:19 ` Wolfram Sang
2021-06-27 10:27 ` Wolfram Sang
2021-07-13 8:21 ` Jean Delvare
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=YNdIEUpBoToGN7JY@kunai \
--to=wsa@kernel.org \
--cc=jdelvare@suse.de \
--cc=leonard.crestez@intel.com \
--cc=linux-i2c@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).