mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bryan Freed <bfreed@chromium.org>
To: linux-kernel@vger.kernel.org
Cc: jic23@cam.ac.uk, gregkh@suse.de, rklein@nvidia.com,
	linux-iio@vger.kernel.org, Bryan Freed <bfreed@chromium.org>
Subject: [PATCH 0/4] Apply these staging:iio patches to staging-next.
Date: Thu,  7 Jul 2011 12:01:53 -0700	[thread overview]
Message-ID: <1310065317-3872-1-git-send-email-bfreed@chromium.org> (raw)

These patches are made from
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging-2.6.git staging-next
instead of
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/
as the previous patches were.

Found another bug there, so there are 4 patches instead of 3.

Bryan Freed (4):
  staging:iio: Reorder channel type strings to match the iio.h enums.
  staging:iio: Add an iio channel type string to support proximity
    sensors.
  staging:iio:light:isl29018: Convert some of the isl29018 driver to
    the new iio_chan_spec framework.
  staging:iio:light:isl29018: Fix the "Init of isl29018 fails" failure.

 drivers/staging/iio/industrialio-core.c |   11 +-
 drivers/staging/iio/light/isl29018.c    |  174 ++++++++++++++----------------
 2 files changed, 87 insertions(+), 98 deletions(-)

-- 
1.7.3.1


             reply	other threads:[~2011-07-07 19:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-07 19:01 Bryan Freed [this message]
2011-07-07 19:01 ` [PATCH v2 1/4] staging:iio: Reorder channel type strings to match the iio.h enums Bryan Freed
2011-07-07 19:01 ` [PATCH v2 2/4] staging:iio: Add an iio channel type string to support proximity sensors Bryan Freed
2011-07-07 19:01 ` [PATCH v2 3/4] staging:iio:light:isl29018: Convert some of the isl29018 driver to the new iio_chan_spec framework Bryan Freed
2011-07-07 19:01 ` [PATCH v1 4/4] staging:iio:light:isl29018: Fix the "Init of isl29018 fails" failure Bryan Freed

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=1310065317-3872-1-git-send-email-bfreed@chromium.org \
    --to=bfreed@chromium.org \
    --cc=gregkh@suse.de \
    --cc=jic23@cam.ac.uk \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rklein@nvidia.com \
    /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

all inboxes | Powered by JetHome®