From: Jean Delvare <jdelvare@suse.de>
To: Linux I2C <linux-i2c@vger.kernel.org>
Cc: Wolfram Sang <wsa+renesas@sang-engineering.com>,
Peter Korsgaard <peter@korsgaard.com>,
Chris Packham <chris.packham@alliedtelesis.co.nz>
Subject: Upcoming release of i2c-tools (will be 4.3)
Date: Thu, 15 Jul 2021 16:15:20 +0200 [thread overview]
Message-ID: <20210715161520.3830c3d1@endymion> (raw)
Hi all,
Due to a regression in i2c-tools 4.2, we decided to hurry the release
of i2c-tools 4.3 even though there aren't that many changes queued.
Well there are still a few nice new features so the update will be
worth it. Here's what the CHANGES file has to say about what's coming:
decode-dimms: Attempt to decode LPDDR3 modules
eeprom, eepromer: Removed the tools in favor of eeprog
i2cdetect: Sort the bus list by number
i2cdump: Add range support to I2C block mode
Deprecate SMBus block mode
i2cget: Add support for I2C block read
Add support for SMBus block read
i2ctransfer: Reverted check for returned length from driver
I will tag and release v4.3 next week. Until then, please give it good
testing if you can, and report any issue.
Thanks,
--
Jean Delvare
SUSE L3 Support
reply other threads:[~2021-07-15 14:15 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20210715161520.3830c3d1@endymion \
--to=jdelvare@suse.de \
--cc=chris.packham@alliedtelesis.co.nz \
--cc=linux-i2c@vger.kernel.org \
--cc=peter@korsgaard.com \
--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 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).