From: "Jean Delvare" <khali@linux-fr.org>
To: vapier.adi@gmail.com, akpm@osdl.org
Cc: i2c@lm-sensors.org, linux-kernel@vger.kernel.org
Subject: Re: [patch] fix typo in i2c smbus documentation
Date: Sat, 30 Dec 2006 10:11:27 +0100 (CET) [thread overview]
Message-ID: <1SnUbvbt.1167469887.0687500.khali@localhost> (raw)
In-Reply-To: <8bd0f97a0612272039l15fb2484v8ebbc1065adab9e2@mail.gmail.com>
Hi Mike,
On 12/28/2006, Mike Frysinger wrote:
> the i2c smbus documentation has a typo ... when it describes the
> "SMBus Write Word Data" function, it says that it is meant to "read
> from a device" when in reality it should obviously be writing to the
> device
Good catch, applied, thanks. I've also backported this fix to i2c-SVN
and linux-2.4, as they also had the mistake.
> btw, the i2c/smbus docs in Documentation/i2c/ are superb, thanks all :)
You're welcome :)
--
Jean Delvare
prev parent reply other threads:[~2006-12-30 9:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-28 4:39 [patch] fix typo in i2c smbus documentation Mike Frysinger
2006-12-30 9:11 ` 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=1SnUbvbt.1167469887.0687500.khali@localhost \
--to=khali@linux-fr.org \
--cc=akpm@osdl.org \
--cc=i2c@lm-sensors.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vapier.adi@gmail.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