From: Wolfram Sang <wsa@the-dreams.de>
To: Sam Hansen <hansens@google.com>
Cc: linux-i2c@vger.kernel.org, corbet@lwn.net,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Jean Delvare <jdelvare@suse.de>
Subject: Re: [PATCH] Documentation/i2c: sync docs with current state of i2c-tools.
Date: Fri, 13 Apr 2018 00:24:57 +0200 [thread overview]
Message-ID: <20180412222457.x4jdwt27ylgi74o3@katana> (raw)
In-Reply-To: <20180412213342.138010-1-hansens@google.com>
[-- Attachment #1: Type: text/plain, Size: 1664 bytes --]
Hi,
On Thu, Apr 12, 2018 at 02:33:42PM -0700, Sam Hansen wrote:
> Currently, Documentation/i2c/dev-interface describes the use of i2c_smbus_*
> helper routines as static inlined functions provided by linux/i2c-dev.h. Work
> has been done to refactor the linux/i2c-dev.h file in the i2c-tools project
> out into its own library. As a result, these docs have become stale.
Thanks for fixing this!
> This patch corrects the discrepancy and directs the reader to the i2c-tools
> project for more information. Additionally, some trailing-whitespace cleanups
> were made.
Minor nit: Having the whitespace changes in a seperate patch is a tad
easier to review.
> - /* Using I2C Write, equivalent of
> + /* Using I2C Write, equivalent of
> i2c_smbus_write_word_data(file, reg, 0x6543) */
Maybe change to Kernel coding style comments while here?
> - Not meant to be called directly; instead, use the access functions
> - below.
> + If possible, use the provided i2c_smbus_* methods described below in favor
> + of issuing direct ioctls.
Why this change?
> -The above functions are all inline functions, that resolve to calls to
> -the i2c_smbus_access function, that on its turn calls a specific ioctl
> -with the data in a specific format. Read the source code if you
> -want to know what happens behind the screens.
> +The above functions are made available by linking against the libi2c library,
> +which is provided by the i2c-tools project. See:
> +https://git.kernel.org/pub/scm/utils/i2c-tools/i2c-tools.git/.
This is fine with me. Maybe Jean has a comment on this?
Kind regards,
Wolfram
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-04-12 22:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-12 21:33 [PATCH] Documentation/i2c: sync docs with current state of i2c-tools Sam Hansen
2018-04-12 22:24 ` Wolfram Sang [this message]
2018-04-13 12:13 ` Jean Delvare
2018-04-13 16:02 ` Sam Hansen
2018-04-13 16:44 ` [PATCH v2 1/3] Documentation/i2c: whitespace cleanup Sam Hansen
2018-04-13 16:44 ` [PATCH v2 2/3] Documentation/i2c: sync docs with current state of i2c-tools Sam Hansen
2018-04-13 16:50 ` Wolfram Sang
2018-04-13 16:44 ` [PATCH v2 3/3] Documentation/i2c: adopt kernel commenting style in examples Sam Hansen
2018-04-13 16:50 ` Wolfram Sang
2018-04-13 17:39 ` Sam Hansen
2018-04-13 16:50 ` [PATCH v2 1/3] Documentation/i2c: whitespace cleanup Wolfram Sang
2018-04-13 18:49 ` [PATCH] Documentation/i2c: sync docs with current state of i2c-tools Jean Delvare
2018-04-13 23:32 ` Sam Hansen
2018-04-14 6:27 ` Wolfram Sang
2018-04-17 19:17 ` Sam Hansen
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=20180412222457.x4jdwt27ylgi74o3@katana \
--to=wsa@the-dreams.de \
--cc=corbet@lwn.net \
--cc=hansens@google.com \
--cc=jdelvare@suse.de \
--cc=linux-doc@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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