From mboxrd@z Thu Jan 1 00:00:00 1970 From: Borislav Petkov Subject: Re: More cpufreq breakage Date: Sat, 23 Mar 2013 19:50:45 +0100 Message-ID: <20130323185045.GA4801@pd.tnic> References: <20130323134541.GA10811@pd.tnic> <5152799.d8sLDQMJWT@vostro.rjw.lan> <20130323160644.GC10811@pd.tnic> Mime-Version: 1.0 Return-path: DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=alien8.de; s=alien8; t=1364064646; bh=6+DRrH4H6kVymljuE7N4BSNDc5MQp3hS+lHnmaWUBto=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:In-Reply-To; b=Kah+eGNLEUfxLfJhHQV1b6qPS3d+s2FwVBgyaE fXmXmqbqzfQp8MAmK9X9XRUr4a4pRDzFPQB5+6z1RPbrEBIs48ttXfu6/GXEh54ZcC7 zk11CNe3W+4a04NWdLnMO0U9BmmtShzD/DRqbLlZPmwie/R5VijF0XvqAY1hZmdAYA= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=alien8.de; s=alien8; t=1364064646; bh=6+DRrH4H6kVymljuE7N4BSNDc5MQp3hS+lHnmaWUBto=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:In-Reply-To; b=Kah+eGNLEUfxLfJhHQV1b6qPS3d+s2FwVBgyaE fXmXmqbqzfQp8MAmK9X9XRUr4a4pRDzFPQB5+6z1RPbrEBIs48ttXfu6/GXEh54ZcC7 zk11CNe3W+4a04NWdLnMO0U9BmmtShzD/DRqbLlZPmwie/R5VijF0XvqAY1hZmdAYA= Content-Disposition: inline In-Reply-To: Sender: cpufreq-owner@vger.kernel.org List-ID: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Viresh Kumar Cc: 1i5t5.duncan@cox.net, "Rafael J. Wysocki" , bugzilla-daemon@bugzilla.kernel.org, Andre Przywara , cpufreq@vger.kernel.org, Lists linaro-kernel , Thomas Renninger On Sat, Mar 23, 2013 at 10:34:28PM +0530, Viresh Kumar wrote: > And that is already caused recently? 3.8.3 is fine and there are no cpufreq patches in v3.8..v3.8.3. Which would mean, plain v3.8 is also fine. Which means, the breakage must've come in during the merge window. -- Regards/Gruss, Boris. Sent from a fat crate under my desk. Formatting is fine. --