[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20110114181746.GM15996@n2100.arm.linux.org.uk>
Date: Fri, 14 Jan 2011 18:17:46 +0000
From: Russell King - ARM Linux <linux@....linux.org.uk>
To: Nicolas Ferre <nicolas.ferre@...el.com>
Cc: "'linux-arm-kernel@...ts.infradead.org'"
<linux-arm-kernel@...ts.infradead.org>,
Linux Kernel list <linux-kernel@...r.kernel.org>,
Igor Plyatov <plyatov@...il.com>,
Andrew Victor <linux@...im.org.za>,
Jean-Christophe PLAGNIOL-VILLARD <plagnioj@...osoft.com>,
Sergio Tanzilli <tanzilli@...esystems.it>
Subject: Re: [GIT PULL] AT91: patches for v2.6.38-rc1
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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists