From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Laxman Dewangan <ldewangan@nvidia.com>
Cc: Axel Lin <axel.lin@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Mike Rapoport <mike@compulab.co.il>,
Cyril Chemparathy <cyril@ti.com>,
Graeme Gregory <gg@slimlogic.co.uk>, Liam Girdwood <lrg@ti.com>
Subject: Re: [PATCH] regulator: Group TI TPSxxxxx regulators together
Date: Tue, 21 Feb 2012 09:53:10 +0000 [thread overview]
Message-ID: <20120221095309.GB3079@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <4F432D7A.7030805@nvidia.com>
[-- Attachment #1: Type: text/plain, Size: 494 bytes --]
On Tue, Feb 21, 2012 at 11:06:58AM +0530, Laxman Dewangan wrote:
> On Tuesday 21 February 2012 10:14 AM, Axel Lin wrote:
> >Group TI TPSxxxxx regulators together and sort them in alphabetical order.
> >This change makes it easier for users to find config options.
> Should we only arrange the tps regulators or all regulators in
> alphabetical order?
> I will prefer to arrange all which inherently will arrange tps as
> all ti regulators start with tps..
We should just sort the whole list.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-02-21 9:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-21 4:44 [PATCH] regulator: Group TI TPSxxxxx regulators together Axel Lin
2012-02-21 5:36 ` Laxman Dewangan
2012-02-21 5:55 ` Axel Lin
2012-02-21 9:53 ` Mark Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-04-15 0:57 Axel Lin
2011-04-15 10:00 ` Mark Brown
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=20120221095309.GB3079@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=axel.lin@gmail.com \
--cc=cyril@ti.com \
--cc=gg@slimlogic.co.uk \
--cc=ldewangan@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@ti.com \
--cc=mike@compulab.co.il \
/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).