From: Jonathan Corbet <corbet@lwn.net>
To: "Cengiz C." <cengizc@gmail.com>
Cc: Wolfram Sang <wsa@the-dreams.de>,
linux-i2c@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] i2c: update i2c-dev.h warning in documentation
Date: Thu, 21 Dec 2017 12:38:09 -0700 [thread overview]
Message-ID: <20171221123809.40311490@lwn.net> (raw)
In-Reply-To: <CANp8-fy-mOUpMgR6F3j6k53gpAHh+TxiKdSaXFfqimcAwe_y3g@mail.gmail.com>
On Tue, 12 Dec 2017 19:43:09 +0300
"Cengiz C." <cengizc@gmail.com> wrote:
> `Documentation/i2c/dev-interface` gives examples for accessing i2c from
> userspace.
>
> There's a note that warns developers about the two `i2c-dev.h` header
> files which were shipped with the kernel and i2c-tools separately.
>
> However, following i2c-tools commits suggest that the header files are now
> identical (in functionality) and `i2c_*` helper functions are now defined
> in a separate header called `i2c/smbus.h`, which is distributed with
> i2c-tools:
>
> commit 652619121974 ("Minimize differences with kernel flavor")
> commit 93caf007f4cb ("Move SMBus helper functions to include/i2c/smbus.h")
>
> Thus, I've converted the warning paragraph into a historical note and
> updated the suggested header files.
>
> Signed-off-by: Cengiz Can <cengizc@gmail.com>
Applied to the docs tree, thanks. Note that the patch was wrapped by your
mailer and I had to fix it up; that would be nice to avoid in the future.
Thanks,
jon
next prev parent reply other threads:[~2017-12-21 19:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-09 20:10 [PATCH] i2c: update i2c-dev.h warning in documentation Cengiz Can
2017-12-11 23:20 ` Jonathan Corbet
2017-12-12 16:43 ` [PATCH v2] " Cengiz C.
2017-12-21 19:38 ` Jonathan Corbet [this message]
2017-12-21 20:49 ` Cengiz Can
2017-12-21 20:54 ` Jonathan Corbet
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=20171221123809.40311490@lwn.net \
--to=corbet@lwn.net \
--cc=cengizc@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wsa@the-dreams.de \
/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).