All of lore.kernel.org
 help / color / mirror / Atom feed
From: Laxman Dewangan <ldewangan@nvidia.com>
To: jic23@cam.ac.uk, gregkh@linuxfoundation.org, max@stro.at,
	jbrenner@taosinc.com, bfreed@chromium.org, lars@metafoo.de,
	grundler@chromium.org
Cc: linux-iio@vger.kernel.org, devel@driverdev.osuosl.org,
	linux-kernel@vger.kernel.org,
	Laxman Dewangan <ldewangan@nvidia.com>
Subject: [PATCH V4 0/2] staging: iio: light: use regmap in isl29018 for register access
Date: Fri, 20 Apr 2012 12:57:36 +0530	[thread overview]
Message-ID: <1334906858-25578-1-git-send-email-ldewangan@nvidia.com> (raw)


This is patch series for using regmap framework for accessing device register.
THe first patch is for using tab for ndenting and second patch is for 
using regmap apis for register accesses.

Changes from V2: 
 Taken care of Lars's review comment.

Changes from V3:
Taken care of Lars's and Grant's comment about COMMAND1 register access.
-Use regmap_write() for ADD_COMMAND1 and keeping this as volatile.


Laxman Dewangan (2):
  staging: iio: light: convert multiple spaces to tab
  staging: iio: light: isl29018: use regmap for register access

 drivers/staging/iio/light/Kconfig    |   19 ++--
 drivers/staging/iio/light/isl29018.c |  178 +++++++++++++++++-----------------
 2 files changed, 100 insertions(+), 97 deletions(-)


             reply	other threads:[~2012-04-20  7:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-20  7:27 Laxman Dewangan [this message]
2012-04-20  7:27 ` [PATCH V4 1/2] staging: iio: light: convert multiple spaces to tab Laxman Dewangan
2012-04-20 11:22   ` Lars-Peter Clausen
2012-04-20 15:52     ` Greg KH
2012-04-20  7:27 ` [PATCH V4 2/2] staging: iio: light: isl29018: use regmap for register access Laxman Dewangan
2012-04-20 15:04   ` Grant Grundler

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=1334906858-25578-1-git-send-email-ldewangan@nvidia.com \
    --to=ldewangan@nvidia.com \
    --cc=bfreed@chromium.org \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=grundler@chromium.org \
    --cc=jbrenner@taosinc.com \
    --cc=jic23@cam.ac.uk \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=max@stro.at \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.