The CI autopackaged TI 3.1 kernels all land here: https://github.com/jcrigby/packaged-linux-linaro-3.1-ci/commits/lt-omap/
All 3.1 LT and non LT kernel land there in different branches but each branch gets overwritten with each new merge so you need the tag to find a particular release. On Fri, Jan 13, 2012 at 9:50 AM, Dave Martin <dave.mar...@linaro.org> wrote: > On Fri, Jan 13, 2012 at 3:52 PM, John Rigby <john.ri...@linaro.org> wrote: >> On Fri, Jan 13, 2012 at 6:32 AM, Dave Martin <dave.mar...@linaro.org> wrote: >>> For everyone who packages kernel trees: >>> >>> >>> I've had some questions about getting the source for linaro kernel >>> packaged, and it seems that this is still not straightforward: >>> >> ... >> >> This seems reasonable to me. This month we are adding CI auto >> packaging/building for LT kernels so I will add the Vcs-Git setting to >> these CI scripts. > > > I think at the moment, we're just pasting it from the vanilla kernel > packaging, which is why we end up with a pointer to the wrong tree > (but that's partly guesswork on my part) > > Do you know if the TI packaged kernels already in a tree somewhere? I > had someone trying to find that specifically. > > Cheers > ---Dave _______________________________________________ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
