From: plagnioj@jcrosoft.com (Jean-Christophe PLAGNIOL-VILLARD)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: sort select statements alphanumerically
Date: Sun, 7 Oct 2012 17:41:15 +0200 [thread overview]
Message-ID: <20121007154115.GD12801@game.jcrosoft.org> (raw)
In-Reply-To: <20121007133048.GE28061@n2100.arm.linux.org.uk>
On 14:30 Sun 07 Oct , Russell King - ARM Linux wrote:
> On Sun, Oct 07, 2012 at 03:14:40PM +0200, Jean-Christophe PLAGNIOL-VILLARD wrote:
> > On 17:22 Sat 06 Oct , Russell King wrote:
> > > This commit is likely to change as we get closer to the end of the merge
> > > window, as other changes get merged into Linus' tree. I will be refreshing
> > > this from time to time, and keeping it out of linux-next, as it will cause
> > > more pain than its worth to put it into linux-next.
> > >
> > > Anyone who wants to give this a review to check that it's correct are welcome,
> > > but I don't think it would be appropriate to collect attributation tags for
> > > it, as this won't be the final patch.
> > >
> > > This patch is intentionally broken to prevent Linus from applying it - this
> > > is information only!
> > >
> > > Anyone who wants to apply it can do so by first running this patch through:
> > >
> > > sed 's/^-- /@@ /'
> > >
> > > arch/arm/Kconfig | 399 ++++++++++++++++++-------------------
> > > arch/arm/common/Kconfig | 4 +-
> > > arch/arm/mach-at91/Kconfig | 26 ++--
> > this maybe conflict with pinctrl support
>
> Of course it will - and this tells me that you did not read the comments
> I left before the diffstat. It's almost guaranteed to conflict with
> virtually all the changes going into this merge window.
>
> > Acked-by: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
>
> And this also confirms that too; I said I didn't want to add attributations
> to it because you aren't going to be acking the patch which will eventually
> be committed.
>
> In sort, this patch _will_ be recreated by the script at the end of the
> merge window, and whatever that patch ends up being is what will get
> merged. It's very likely (because of the inherent conflicts in doing
> this) that it _will_ be different from this one.
>
> What that means is if I add (your) acked-by to it, I will be adding it
> to a different patch to the one you've sent this to.
>
> What I want people to do with this is review it and make sure that the
> script hasn't created any obvious mistakes; I've already done that but
> the more eyes we get on it the better.
I did read it I just point it out so if people try to apply over it then known
and just point out that I see no issue on at91
Best Regards,
J.
next prev parent reply other threads:[~2012-10-07 15:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-06 16:22 [PATCH] ARM: sort select statements alphanumerically Russell King
2012-10-07 13:14 ` Jean-Christophe PLAGNIOL-VILLARD
2012-10-07 13:30 ` Russell King - ARM Linux
2012-10-07 15:41 ` Jean-Christophe PLAGNIOL-VILLARD [this message]
2012-10-08 2:50 ` Eric Miao
2012-10-08 7:53 ` Russell King - ARM Linux
2012-10-08 15:29 ` Shawn Guo
2012-10-08 15:45 ` Russell King - ARM Linux
2012-10-09 6:18 ` Barry Song
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=20121007154115.GD12801@game.jcrosoft.org \
--to=plagnioj@jcrosoft.com \
--cc=linux-arm-kernel@lists.infradead.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).