Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754130Ab3IKK70 (ORCPT ); Wed, 11 Sep 2013 06:59:26 -0400 Received: from mail-qe0-f44.google.com ([209.85.128.44]:34622 "EHLO mail-qe0-f44.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751269Ab3IKK7Y (ORCPT ); Wed, 11 Sep 2013 06:59:24 -0400 MIME-Version: 1.0 In-Reply-To: References: Date: Wed, 11 Sep 2013 16:29:23 +0530 Message-ID: Subject: Re: [PATCH 0/5] CPUFreq: Last set of updates for 3.13 From: Viresh Kumar To: Amit Kucheria Cc: "Rafael J. Wysocki" , Lists linaro-kernel , Linux PM list , Patch Tracking , Linux Kernel Mailing List , "cpufreq@vger.kernel.org" , Lists LAKML Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1191 Lines: 34 On 11 September 2013 16:23, Amit Kucheria 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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/