All of lore.kernel.org
 help / color / mirror / Atom feed
From: Samuel Ortiz <sameo@linux.intel.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Axel Lin <axel.lin@gmail.com>,
	linux-kernel@vger.kernel.org,
	Mark Brown <broonie@opensource.wolfsonmicro.com>
Subject: Re: [PATCH] mfd: Sort Kconfig entries for mfd drivers
Date: Mon, 16 Apr 2012 19:44:10 +0200	[thread overview]
Message-ID: <20120416174410.GT24130@sortiz-mobl> (raw)
In-Reply-To: <CACRpkda2M1CWJymf2QBmpKzVo_+UGMEV+sj2aF-vjbHStwrtAw@mail.gmail.com>

Hi Axel, Linus,

On Fri, Apr 13, 2012 at 02:35:48PM +0200, Linus Walleij wrote:
> On Thu, Apr 12, 2012 at 4:50 AM, Axel Lin <axel.lin@gmail.com> wrote:
> 
> > Sort Kconfig entries by chip vendor name first, then driver name.
> > Having the Kconfig entries sorted makes it easier for users to find the
> > driver they want to enable.
> > This change also encourages new coming drivers to be put in proper location
> > rather than to be added at random location.
> >
> > Signed-off-by: Axel Lin <axel.lin@gmail.com>
> > ---
> > Hi Samuel,
> > I generate this patch against linux-next 20120411.
> > If you think this patch is ok, pls apply this one and
> > ignore my previous patch "mfd: Move MFD_TPS65090 and
> > TPS65911_COMPARATOR Kconfig entries to proper location".
> 
> This is going to cause a number of merge conflicts for upcoming
> patches from my side, I'd really like this to go into the -rc:s
> if accepted so I can rely on it being present as a merge base.
It's definitely too late for rc:s, so I'll postpone this one for after Linus
code gets merged.

Cheers,
Samuel.

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

      reply	other threads:[~2012-04-16 17:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-12  2:50 [PATCH] mfd: Sort Kconfig entries for mfd drivers Axel Lin
2012-04-13 12:35 ` Linus Walleij
2012-04-16 17:44   ` 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=20120416174410.GT24130@sortiz-mobl \
    --to=sameo@linux.intel.com \
    --cc=axel.lin@gmail.com \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.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.