From: gregkh@linuxfoundation.org (Greg KH) Date: Mon, 14 Oct 2013 11:20:06 -0700 Subject: [PATCH stable] ARM: tegra: unify Tegra's Kconfig a bit more In-Reply-To: <525C33D1.4080509@nvidia.com> References: <1380917411-25869-1-git-send-email-swarren@wwwdotorg.org> <20131005233833.GA18223@kroah.com> <52525247.9060609@nvidia.com> <52539F98.2030307@nvidia.com> <20131010231135.GF4301@kroah.com> <525C33D1.4080509@nvidia.com> Message-ID: <20131014182006.GB18058@kroah.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Mon, Oct 14, 2013 at 11:11:29AM -0700, Paul Walmsley wrote: > Hi Greg, > > On 10/10/2013 04:11 PM, Greg KH wrote: > >On Mon, Oct 07, 2013 at 11:00:56PM -0700, Paul Walmsley wrote: > > > >>Well, here's a public link for it: > >> > >>http://nvt.pwsan.com/pub/linux-stable/testlogs/ > >> > >>So far it's seeded with v3.11.[34]. It should update automatically > >>as new releases come out. So far the tests are quite basic (build + > >>boot to minimal userspace). Please let Stephen and I know if you > >>have any comments or suggestions. > >That's great to see. Testing the -rc stable releases would be great, to > >find if I break anything, as I don't have Tegra hardware to test them > >out on. > > Could you point out the -rc stable releases that you're referring > to? Took a look at the linux-stable.git and stable-queue.git trees > but was unsure what matched that description. The -rc releases do not end up in a git tree, they show up in the kernel.org/pub/linux/kernel/v3.0/stable-review/ directory when I announce a -rc release is out for testing. > Would this be something like applying the queue-* patches and > testing on a nightly basis? Yes, that is good to do as well, as that is what the -rc releases are created from. thanks, greg k-h