[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAKohpomFjmfZ5Ce91o1VOhGT33L+jH-5G0NgAQCTFL6v7kNFdw@mail.gmail.com>
Date: Wed, 11 Sep 2013 16:29:23 +0530
From: Viresh Kumar <viresh.kumar@...aro.org>
To: Amit Kucheria <amit.kucheria@...aro.org>
Cc: "Rafael J. Wysocki" <rjw@...k.pl>,
Lists linaro-kernel <linaro-kernel@...ts.linaro.org>,
Linux PM list <linux-pm@...r.kernel.org>,
Patch Tracking <patches@...aro.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
"cpufreq@...r.kernel.org" <cpufreq@...r.kernel.org>,
Lists LAKML <linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH 0/5] CPUFreq: Last set of updates for 3.13
On 11 September 2013 16:23, Amit Kucheria <amit.kucheria@...aro.org> wrote:
> Thanks for the great work cleaning up all the drivers. IIUC, you have
> ~200 patches lined up for the 3.13 merge window.
227 to be precise :)
> That causes some worries.
>
> Can we quickly do the following to get more confidence that there
> won't be wide-spread breakage:
>
> 1. Get all of these into linux-next quickly
Yes, even Myself and Rafael wanted to do that.. And were waiting
for pull request to go for 3.12-rc1..
I am mostly ready with my patches, wouldn't take long time for
me to review those completely before sending them..
> 2. Set up a LAVA[1] job to get linux-next kernels running on boards in our farm
> 3. Run cpufreq functional tests, e.g. PM-QA[2] test suite from Linaro
> with these kernels
That would be nice actually.. Anyway some people would test it on
linux-next, but doing that for few boards by Linaro would be
Awesome..
--
viresh
--
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