From: Guenter Roeck <guenter.roeck-IzeFyvvaP7pWk0Htik3J/w@public.gmane.org>
To: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
Cc: Guenter Roeck <guenter.roeck-IzeFyvvaP7pWk0Htik3J/w@public.gmane.org>
Subject: [PATCH v3 0/6] i2cset changes
Date: Mon, 14 Feb 2011 10:06:07 -0800 [thread overview]
Message-ID: <1297706773-26389-1-git-send-email-guenter.roeck@ericsson.com> (raw)
The following series of patches removes the obsolete means to specify the value mask,
improves parameter error detection for the i2cset command, and cleans up the code a bit.
Note: Patch revision in headline was updated only if the individual patch is either new
or was changed.
v2:
- Split single patch into multiple individual patches
- Included code review feedback
v3:
- For block commands, check for number of arguments only after checking if pec
is supported.
- Report "Too many arguments" instead of "Bad number of arguments".
- Committed blank replacement patch separately
- Check valid range for data value mask (patch #6)
next reply other threads:[~2011-02-14 18:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-14 18:06 Guenter Roeck [this message]
[not found] ` <1297706773-26389-1-git-send-email-guenter.roeck-IzeFyvvaP7pWk0Htik3J/w@public.gmane.org>
2011-02-14 18:06 ` [PATCH v2 1/6] i2cset: Remove deprecated method to provide the value mask Guenter Roeck
2011-02-14 18:06 ` [PATCH v3 2/6] i2cset: Check number of arguments for block data writes Guenter Roeck
2011-02-14 18:06 ` [PATCH v2 3/6] i2cset: Abort if value mask is set for block commands Guenter Roeck
2011-02-14 18:06 ` [PATCH v3 4/6] i2cset: Ensure that there is no junk after the command/mode parameter Guenter Roeck
2011-02-14 18:06 ` [PATCH v2 5/6] i2cset: Get command/mode before reading data Guenter Roeck
2011-02-14 18:06 ` [PATCH v3 6/6] i2cset: Check range for data value mask Guenter Roeck
2011-02-15 9:45 ` [PATCH v3 0/6] i2cset changes 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=1297706773-26389-1-git-send-email-guenter.roeck@ericsson.com \
--to=guenter.roeck-izefyvvap7pwk0htik3j/w@public.gmane.org \
--cc=khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.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).