devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Samuel Ortiz <sameo@linux.intel.com>
To: Stephen Warren <swarren@wwwdotorg.org>
Cc: Mark Brown <broonie@opensource.wolfsonmicro.com>,
	devicetree-discuss@lists.ozlabs.org,
	linux-kernel@vger.kernel.org, Gyungoh Yoo <jack.yoo@maxim-ic.com>,
	Stephen Warren <swarren@nvidia.com>
Subject: Re: [PATCH V4] mfd: add MAX8907 core driver
Date: Mon, 17 Sep 2012 01:16:08 +0200	[thread overview]
Message-ID: <20120916231608.GM3647@sortiz-mobl> (raw)
In-Reply-To: <1345048126-24054-1-git-send-email-swarren@wwwdotorg.org>

Hi Stephen,

On Wed, Aug 15, 2012 at 10:28:46AM -0600, Stephen Warren wrote:
> From: Gyungoh Yoo <jack.yoo@maxim-ic.com>
> 
> The MAX8907 is an I2C-based power-management IC containing voltage
> regulators, a reset controller, a real-time clock, and a touch-screen
> controller.
> 
> The original driver was written by:
> * Gyungoh Yoo <jack.yoo@maxim-ic.com>
> 
> Various fixes and enhancements by:
> * Jin Park <jinyoungp@nvidia.com>
> * Tom Cherry <tcherry@nvidia.com>
> * Prashant Gaikwad <pgaikwad@nvidia.com>
> * Dan Willemsen <dwillemsen@nvidia.com>
> * Laxman Dewangan <ldewangan@nvidia.com>
> 
> During upstreaming, I (swarren):
> * Converted to regmap.
> * Converted to regmap-irq.
> * Allowed probing from device tree.
> * Renamed from max8907c->max8907, since the driver covers at least the
>   C and B revisions.
> * General cleanup.
> 
> Signed-off-by: Gyungoh Yoo <jack.yoo@maxim-ic.com>
> Signed-off-by: Stephen Warren <swarren@nvidia.com>
> Reviewed-by: Mark Brown <broonie@opensource.wolfsonmicro.com> #v3
Patch applied now, thanks a lot.

Cheers,
Samuel.

-- 
Intel Open Source Technology Centre
http://oss.intel.com/

      parent reply	other threads:[~2012-09-16 23:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-15 16:28 [PATCH V4] mfd: add MAX8907 core driver Stephen Warren
2012-08-24 21:46 ` Stephen Warren
2012-09-16 23:16 ` Samuel Ortiz [this message]

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=20120916231608.GM3647@sortiz-mobl \
    --to=sameo@linux.intel.com \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=jack.yoo@maxim-ic.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=swarren@nvidia.com \
    --cc=swarren@wwwdotorg.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).