public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Laxman Dewangan <ldewangan@nvidia.com>
Cc: sameo@linux.intel.com, lrg@ti.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2 2/2] regulator: tps80031: add regulator driver for tps80031
Date: Fri, 9 Nov 2012 17:15:06 +0000	[thread overview]
Message-ID: <20121109171505.GY23807@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1352118699-24602-3-git-send-email-ldewangan@nvidia.com>

[-- Attachment #1: Type: text/plain, Size: 677 bytes --]

On Mon, Nov 05, 2012 at 06:01:39PM +0530, Laxman Dewangan wrote:
> Add regulator driver for Texas Instrument TPS80031/TPS80032 device.
> TPS80031/ TPS80032 Fully Integrated Power Management with Power
> Path and Battery Charger. It has 5 configurable step-down
> converters, 11 general purpose LDOs, VBUS generator and digital
> output to control regulators.

This looks OK but can't be applied as you're updating the header file
which was added in patch 1 - can you rework so that the header file is
added all at once rather than incrementally please?  For new MFDs this
is easier as the individual drivers can be applied as normal without
needing to all go through one tree.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

      reply	other threads:[~2012-11-09 17:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-05 12:31 [PATCH V2 0/2] tps80031: Add mfd and regulator driver Laxman Dewangan
2012-11-05 12:31 ` [PATCH V2 1/2] mfd: add TI TPS80031 mfd core driver Laxman Dewangan
2012-11-05 12:31 ` [PATCH V2 2/2] regulator: tps80031: add regulator driver for tps80031 Laxman Dewangan
2012-11-09 17:15   ` Mark Brown [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=20121109171505.GY23807@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=ldewangan@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lrg@ti.com \
    --cc=sameo@linux.intel.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