[ Added linaro-dev for a wider diffusion ]

On Wed, 9 Feb 2011, Arnd Bergmann wrote:

> On Monday 07 February 2011, Paul E. McKenney wrote:
> >
> > The February 24th feature freeze is coming up very quickly.  We therefore
> > need any kernel patches that are to be included into the 11.05 Linaro kernel
> > release to be submitted to linaro-dev (CCing nicolas.pitre@linaro.org)
> > as well as upstream as soon as possible.  Otherwise, we cannot guarantee
> > that they will be included in the upcoming Linaro kernel release.
>
> I suppose by submitting upstream, you mean that the patches need to show
> up in one of the trees that are part of linux-next, right?
>
> The development phase for 2.6.38 is closed, and the merge window for 2.6.39
> will not be open until the Linaro feature freeze, so that is the only
> place where patches heading for upstream can go at the moment.

Here's what I intend to do with regard to the Linaro kernel to be used
for the 11.05 release.

I'll create a linaro-2.6.38 tree which will be seeded with v2.6.38-rc5
which should happen sometimes next week.  That will be about the same
level of functionality as what we currently have in linaro-2.6.37 for
the ARM parts, and merging the remaining extra patches found in
linaro-2.6.37 not to be found in 2.6.38 yet should be quite easy.

So if you have more patches that you want to see included in the 11.05
Linaro release then it is a good thing to rebase them to the latest
mainline (currently 2.6.38-rc4) and make sure they are validated and
sent my way _before_ February 24th.  Incidentally, while at it, this
would also be a good time to send those patches to the respective
upstream maintainers for inclusion into the mainline kernel tree during
the upcoming merge window.

Nicolas

_______________________________________________
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev