From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Nicolas Ferre <nicolas.ferre@atmel.com>
Cc: "'linux-arm-kernel@lists.infradead.org'"
<linux-arm-kernel@lists.infradead.org>,
Linux Kernel list <linux-kernel@vger.kernel.org>,
Igor Plyatov <plyatov@gmail.com>,
Andrew Victor <linux@maxim.org.za>,
Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>,
Sergio Tanzilli <tanzilli@acmesystems.it>
Subject: Re: [GIT PULL] AT91: patches for v2.6.38-rc1
Date: Fri, 14 Jan 2011 18:17:46 +0000 [thread overview]
Message-ID: <20110114181746.GM15996@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <4D309278.5010603@atmel.com>
On Fri, Jan 14, 2011 at 07:14:16PM +0100, Nicolas Ferre wrote:
> Le 14/01/2011 19:04, Russell King - ARM Linux :
> > On Fri, Jan 14, 2011 at 07:00:16PM +0100, Nicolas Ferre wrote:
> >> Hi Russell,
> >>
> >> Can you please pull those little changes for AT91? They add two
> >> new boards already discussed on the mailing list and a little
> >> cleanup patch:
> >
> > Has this already been in linux-next?
>
> I must admit that... no.
>
> > We should only be merging new code during a merge window which has
> > already had visibility in linux-next, with the exception of bug fixes
> > and regression fixes.
>
> I understand your point but those are only *board* files that are lying
> around for one or two months.
> I was really wishing to see them included in mainline during merge
> window as they are not core ARM nor AT91 files...
Okay for this time, but please ensure that stuff like this is in
linux-next before the merge window next time so that it can have
some exposure.
prev parent reply other threads:[~2011-01-14 18:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-14 18:00 Nicolas Ferre
2011-01-14 18:04 ` Russell King - ARM Linux
2011-01-14 18:14 ` Nicolas Ferre
2011-01-14 18:17 ` Russell King - ARM Linux [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=20110114181746.GM15996@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@maxim.org.za \
--cc=nicolas.ferre@atmel.com \
--cc=plagnioj@jcrosoft.com \
--cc=plyatov@gmail.com \
--cc=tanzilli@acmesystems.it \
/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
all inboxes | Powered by JetHome®