From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Stephen Warren <swarren@wwwdotorg.org>
Cc: Laxman Dewangan <ldewangan@nvidia.com>,
sameo@linux.intel.com, grant.likely@secretlab.ca,
rob.herring@calxeda.com, swarren@nvidia.com,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
devicetree-discuss@lists.ozlabs.org
Subject: Re: [PATCH] regulator: tps6586x: add support for SYS rail
Date: Sat, 4 Aug 2012 01:52:34 +0100 [thread overview]
Message-ID: <20120804005234.GH4515@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <501AAE55.3080504@wwwdotorg.org>
On Thu, Aug 02, 2012 at 10:44:05AM -0600, Stephen Warren wrote:
> On 08/02/2012 05:16 AM, Laxman Dewangan wrote:
> > .desc = { \
> > + .supply_name = "sys", \
> > .name = "REG-SYS", \
> > .ops = &tps6586x_sys_regulator_ops, \
> > .type = REGULATOR_VOLTAGE, \
> BTW, this patch touches both the regulator and MFD trees. I'm not sure
> who will apply it. I think it relies on the patch to this driver Mark
> recently applied in the regulator tree (for 3.7 I think) doesn't it, at
> least for context?
It varies - it's usually whichever tree the change logically belongs in
(so adding a define for a new regulator in the MFD would go with the
rest of the implementation of a new regulator but a change in the
register I/O interface of the core would go via MFD).
prev parent reply other threads:[~2012-08-04 0:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-02 11:16 [PATCH] regulator: tps6586x: add support for SYS rail Laxman Dewangan
2012-08-02 11:16 ` Laxman Dewangan
2012-08-02 11:40 ` Mark Brown
2012-08-02 11:51 ` Laxman Dewangan
2012-08-02 16:10 ` Mark Brown
[not found] ` <1343906193-8309-1-git-send-email-ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-08-02 16:44 ` Stephen Warren
2012-08-02 16:44 ` Stephen Warren
2012-08-03 6:09 ` Laxman Dewangan
2012-08-04 0:52 ` 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=20120804005234.GH4515@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=ldewangan@nvidia.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rob.herring@calxeda.com \
--cc=sameo@linux.intel.com \
--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 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.