From: Jean Delvare <jdelvare@suse.de>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: Wolfram Sang <wsa+renesas@sang-engineering.com>,
linux-i2c@vger.kernel.org, linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH i2c-tools-3.1] i2c-tools: add new tool 'i2ctransfer'
Date: Fri, 7 Jul 2017 13:43:30 +0200 [thread overview]
Message-ID: <20170707134330.47bd5cbc@endymion> (raw)
In-Reply-To: <20170419181257.bgzi2o4ygwdpquvs@ninjato>
On Wed, 19 Apr 2017 20:12:57 +0200, Wolfram Sang wrote:
> On Fri, Apr 07, 2017 at 02:44:03PM +0200, Wolfram Sang wrote:
> > This tool allows to construct and concat multiple I2C messages into one
> > single transfer. Its aim is to test I2C master controllers, and so there
> > is no SMBus fallback.
> >
> > I've been missing such a tool a number of times now, so I finally got
> > around to writing it myself. As with all I2C tools, it can be dangerous,
> > but it can also be very useful when developing.
> >
> > It has been tested with various Renesas I2C IP cores as well as Tegra,
> > i.MX and AT91.
> >
> > Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
> > ---
>
> Pushed to i2c-tools-3.1.
As usual I'm late to the party... I don't think this should have gone
to branch 3.1 which is a bug-fix only branch. If people want the newest
shiny stuff they should use the master branch. And if it bothers them
that there is no released version of it... well they may be right, and
it suggests it's about time to push a first version of i2c-tools 4 out
the door.
--
Jean Delvare
SUSE L3 Support
prev parent reply other threads:[~2017-07-07 11:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-07 12:44 [PATCH i2c-tools-3.1] i2c-tools: add new tool 'i2ctransfer' Wolfram Sang
2017-04-19 18:12 ` Wolfram Sang
2017-07-07 11:43 ` Jean Delvare [this message]
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=20170707134330.47bd5cbc@endymion \
--to=jdelvare@suse.de \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=wsa+renesas@sang-engineering.com \
--cc=wsa@the-dreams.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 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).