linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Meerwald <pmeerw@pmeerw.net>
To: linux-iio@vger.kernel.org
Cc: jic23@kernel.org
Subject: [PATCH 0/4] iio: missing ABI documentation
Date: Fri,  2 May 2014 17:54:45 +0200	[thread overview]
Message-ID: <1399046089-6616-1-git-send-email-pmeerw@pmeerw.net> (raw)

Hi,

this tried to document some ABI in use for a long time but never
properly documented; I think it is beneficial to say what things
are supposed to be even while certain existing drivers may violate
it

this is meant as an RFC

cheers, p.

Peter Meerwald (4):
  iio: Add intensity including ir and both modifiers to ABI
    documentation ex-post
  iio: Add ABI documentation for illuminance
  iio: Add ABI documentation for proximity
  iio: Fix spelling of illuminance in gp2ap020a00f driver

 Documentation/ABI/testing/sysfs-bus-iio | 29 +++++++++++++++++++++++++++++
 drivers/iio/light/gp2ap020a00f.c        |  8 ++++----
 2 files changed, 33 insertions(+), 4 deletions(-)

-- 
1.9.1

             reply	other threads:[~2014-05-02 15:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-02 15:54 Peter Meerwald [this message]
2014-05-02 15:54 ` [PATCH 1/4] iio: Add intensity including ir and both modifiers to ABI documentation ex-post Peter Meerwald
2014-05-03 10:41   ` Jonathan Cameron
2014-05-02 15:54 ` [PATCH 2/4] iio: Add ABI documentation for illuminance Peter Meerwald
2014-05-03 10:45   ` Jonathan Cameron
2014-05-02 15:54 ` [PATCH 3/4] iio: Add ABI documentation for proximity Peter Meerwald
2014-05-03 10:48   ` Jonathan Cameron
2014-05-03 10:49     ` Jonathan Cameron
2014-05-02 15:54 ` [PATCH 4/4] iio: Fix spelling of illuminance in gp2ap020a00f driver Peter Meerwald
2014-05-03 10:58   ` Jonathan Cameron

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=1399046089-6616-1-git-send-email-pmeerw@pmeerw.net \
    --to=pmeerw@pmeerw.net \
    --cc=jic23@kernel.org \
    --cc=linux-iio@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;
as well as URLs for NNTP newsgroup(s).