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
Subject: Re: [PATCH v3 2/3] Documentation/i2c: sync docs with current state of i2c-tools
Date: Wed, 18 Apr 2018 10:09:27 +0200 [thread overview]
Message-ID: <20180418080927.l56nlorhxkdbmdyu@ninjato> (raw)
In-Reply-To: <20180413174257.139182-2-hansens@google.com>
[-- Attachment #1: Type: text/plain, Size: 584 bytes --]
On Fri, Apr 13, 2018 at 10:42:56AM -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.
>
> This patch corrects the discrepancy and directs the reader to the
> i2c-tools project for more information.
>
> Signed-off-by: Sam Hansen <hansens@google.com>
Applied to for-current, thanks!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-04-18 8:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-13 17:42 [PATCH v3 1/3] Documentation/i2c: whitespace cleanup Sam Hansen
2018-04-13 17:42 ` [PATCH v3 2/3] Documentation/i2c: sync docs with current state of i2c-tools Sam Hansen
2018-04-18 8:09 ` Wolfram Sang [this message]
2018-04-18 8:21 ` Wolfram Sang
2018-04-18 18:17 ` Sam Hansen
2018-04-13 17:42 ` [PATCH v3 3/3] Documentation/i2c: adopt kernel commenting style in examples Sam Hansen
2018-04-18 8:10 ` Wolfram Sang
2018-04-18 8:08 ` [PATCH v3 1/3] Documentation/i2c: whitespace cleanup Wolfram Sang
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=20180418080927.l56nlorhxkdbmdyu@ninjato \
--to=wsa@the-dreams.de \
--cc=corbet@lwn.net \
--cc=hansens@google.com \
--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