From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Jean Delvare <jdelvare@suse.de>
Cc: Peter Korsgaard <peter@korsgaard.com>,
linux-i2c@vger.kernel.org, linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH i2c-tools] Revert "tools: i2ctransfer: add check for returned length from driver"
Date: Fri, 4 Jun 2021 21:21:17 +0200 [thread overview]
Message-ID: <YLp9Lc5Ondu3Gicg@kunai> (raw)
In-Reply-To: <20210604155708.14159db0@endymion>
[-- Attachment #1: Type: text/plain, Size: 926 bytes --]
> Yes I do care. Apparently I wasn't Cc'd on that thread so I wasn't even
> aware that patch existed. It would be very nice if you could bump the
> thread to me (unless there's a way to retrieve it from patchwork that I
> didn't find?)
Sadly, I can't send the whole thread. I thought a had a local archive
collected via gmane, but it seems this is not as complete as I hoped for
:( You can download the patch itself as mbox, however. Check the upper
right corner of the patchwork page. Or search for "mbox".
> If we only want *one* I2C block read at a specified offset then i2cget
> seems more appropriate indeed.
I don't have a clear opinion here. On the one hand, if we want just one
block read, this is more a "get" than a "dump". On the other hand,
i2cdump already has a range-parameter. So, from a user perspective,
keeping i2cget to single values and update the range parameter in
i2cdump might be least confusing?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-06-04 19:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-09 11:05 [PATCH i2c-tools] Revert "tools: i2ctransfer: add check for returned length from driver" Wolfram Sang
2021-02-26 16:43 ` Jean Delvare
2021-03-10 20:46 ` Wolfram Sang
2021-04-10 8:14 ` Peter Korsgaard
2021-04-13 12:54 ` Wolfram Sang
2021-04-21 20:01 ` Peter Korsgaard
2021-05-21 11:21 ` Jean Delvare
2021-05-25 20:36 ` Wolfram Sang
2021-06-02 9:03 ` Jean Delvare
2021-06-02 16:25 ` Wolfram Sang
2021-06-04 13:57 ` Jean Delvare
2021-06-04 19:21 ` Wolfram Sang [this message]
2021-06-08 12:22 ` Jean Delvare
2021-06-08 12:26 ` Wolfram Sang
2021-05-21 11:16 ` Jean Delvare
2021-03-07 5:42 ` 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=YLp9Lc5Ondu3Gicg@kunai \
--to=wsa+renesas@sang-engineering.com \
--cc=jdelvare@suse.de \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=peter@korsgaard.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.