From: Jonathan Cameron <jic23@kernel.org>
To: gregkh@linuxfoundation.org
Cc: linux-iio@vger.kernel.org, Jonathan Cameron <jic23@kernel.org>
Subject: [PATCH 0/4] IIO: Another set of buglets plus cleanups.
Date: Fri, 13 Apr 2012 10:24:17 +0100 [thread overview]
Message-ID: <1334309061-21073-1-git-send-email-jic23@kernel.org> (raw)
Hi Greg,
A fairly trivial set that no one has reported any problems with.
Only difference in here from version sent to list was an accidentally
included binary file pointed out by Maxime Ripard.
Thanks,
Jonathan
Jonathan Cameron (4):
staging:iio:light:tsl2563 channel spec buglet / always reading same
adc.
staging:iio:Documentation: Fix a cut and paste error.
staging:iio:iio_core.h make less dependent on other included headers
staging:iio: chan_spec - take extend_name constant.
drivers/staging/iio/Documentation/sysfs-bus-iio | 8 ++++----
drivers/staging/iio/iio.h | 2 +-
drivers/staging/iio/iio_core.h | 6 ++++++
drivers/staging/iio/light/tsl2563.c | 3 ++-
4 files changed, 13 insertions(+), 6 deletions(-)
next reply other threads:[~2012-04-13 9:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-13 9:24 Jonathan Cameron [this message]
2012-04-13 9:24 ` [PATCH 1/4] staging:iio:light:tsl2563 channel spec buglet / always reading same adc Jonathan Cameron
2012-04-13 9:24 ` [PATCH 2/4] staging:iio:Documentation: Fix a cut and paste error Jonathan Cameron
2012-04-13 9:24 ` [PATCH 3/4] staging:iio:iio_core.h make less dependent on other included headers Jonathan Cameron
2012-04-13 9:24 ` [PATCH 4/4] staging:iio: chan_spec - take extend_name constant Jonathan Cameron
-- strict thread matches above, loose matches on Subject: below --
2012-04-10 20:17 [PATCH 0/4] IIO: Another set of buglets plus cleanups 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=1334309061-21073-1-git-send-email-jic23@kernel.org \
--to=jic23@kernel.org \
--cc=gregkh@linuxfoundation.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).