From: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
To: David Brownell <david-b-yBeKhBN/0LDR7s880joybQ@public.gmane.org>
Cc: i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org
Subject: Re: [patch 2.6.25-rc1] i2c: improve smbus-protocol documentation
Date: Sat, 10 May 2008 09:25:08 +0200 [thread overview]
Message-ID: <20080510092508.6f9bd2d2@hyperion.delvare> (raw)
In-Reply-To: <200805031750.34306.david-b-yBeKhBN/0LDR7s880joybQ@public.gmane.org>
Hi David,
On Sat, 3 May 2008 17:50:33 -0700, David Brownell wrote:
> Improve the smbus-protocol documentation file somewhat:
>
> - Use the names of the SMBus protocol operations (from the 2.0
> specification), not made-up-for-Linux names.
>
> - Add the name of the call used to execute each operation ... and
> point out that there are mismatches, where functions execute
> different protocol operations than their names specify.
>
> The most confusing examples are that "Read Byte" isn't executed by
> i2c_smbus_read_byte(), and that "Write Byte" isn't executed by
> i2c_smbus_write_byte(). When coding, that's not as bad as it may
> seem; but that case would seem to be worth fixing.
>
> Signed-off-by: David Brownell <dbrownell-Rn4VEauK+AKRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
> ---
> As doc-only, this is appropriate for bundling with any I2C fixes
> before the 2.6.26-final code freeze. Note that this doesn't address
> the confusion between "command" and "register" in this text, though
> in some cases it reduces confusion between "command" and "protocol
> operation" or "function call".
>
> Documentation/i2c/smbus-protocol | 75 +++++++++++++++++++++------------------
> 1 file changed, 42 insertions(+), 33 deletions(-)
Applied, thanks for doing this. This patch will be included in my next
batch to Linus (probably today or tomorrow.)
--
Jean Delvare
_______________________________________________
i2c mailing list
i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org
http://lists.lm-sensors.org/mailman/listinfo/i2c
prev parent reply other threads:[~2008-05-10 7:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-04 0:50 [patch 2.6.25-rc1] i2c: improve smbus-protocol documentation David Brownell
[not found] ` <200805031750.34306.david-b-yBeKhBN/0LDR7s880joybQ@public.gmane.org>
2008-05-10 7:25 ` 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=20080510092508.6f9bd2d2@hyperion.delvare \
--to=khali-puyad+kwke1g9huczpvpmw@public.gmane.org \
--cc=david-b-yBeKhBN/0LDR7s880joybQ@public.gmane.org \
--cc=i2c-GZX6beZjE8VD60Wz+7aTrA@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