From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1753929Ab3A3UX5 (ORCPT <rfc822;w@1wt.eu>);
	Wed, 30 Jan 2013 15:23:57 -0500
Received: from mout.web.de ([212.227.15.3]:59898 "EHLO mout.web.de"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1751736Ab3A3UXz (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
	Wed, 30 Jan 2013 15:23:55 -0500
From: Thomas Schlichter <thomas.schlichter@web.de>
To: Daniel Lezcano <daniel.lezcano@linaro.org>
Cc: sedat.dilek@gmail.com, Linux PM List <linux-pm@lists.linux-foundation.org>,
        LKML <linux-kernel@vger.kernel.org>,
        Linux ACPI <linux-acpi@vger.kernel.org>,
        "Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: [PATCH] cpuidle: fix new C-states not functional after AC disconnect
Date: Wed, 30 Jan 2013 21:23:39 +0100
Message-ID: <8501010.gC0S6gjEMf@netbook>
User-Agent: KMail/4.9.4 (Linux/3.8.0-rc5-00001-gde1fba0-dirty; KDE/4.9.4; i686; ; )
In-Reply-To: <50F31CB9.4010905@linaro.org>
References: <CA+icZUXCObXMqVMNLFL58fZCBzo8dv+mqa7Ue_+jVfAdaYG45A@mail.gmail.com> <CA+icZUUUjQTVunewhv+wEsrvyD4FsG9riHa8MRrZdMufyttA4w@mail.gmail.com> <50F31CB9.4010905@linaro.org>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
X-Provags-ID: V02:K0:mq5rl6OqyW+8Ad/0qEaPfBcvR0sCL4yR8/C6q9MXXcA
 U/sW88HXhpmB7wNblkOxX5ZtJVFaDbBq3+c44jjcoZY2jSqSCH
 8WQBAJLFm6LUpTD/ahG33j9E0PiLtABvcpZcefEJ3q3HWf7X3m
 D1lWHa3p+ggZ2RfiXae7DIYkvovvb/hHZdwT4YbD1IVNtggQBN
 E/O6i1M4PoxJZFRK4IlUSeSi61zSf7crhO9orLS4Yw=
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

Am Sonntag, 13. Januar 2013, 21:44:41 schrieb Daniel Lezcano:
> On 01/13/2013 09:36 PM, Sedat Dilek wrote:
> > 0001: Refreshed 1-2 as v3 against Linux v3.8-rc3.
> > 0002: v2 of 2-2 applied cleanly after 1-2 was refreshed!
> 
> Hi Sedat,
> 
> for the moment, you should use only the 1/2 because 2/2 (which is an
> optimization) is wrong.

Hi Daniel,

thanks again for this patch, this together with my patch finally fix the bug.
Now I recognized that only my patch was also sent to stable (thanks Rafael), 
yours not. So the bug is not completely fixed in 3.4 and 3.7.

Is there a reason for not sending this to stable, too?

Kind regards,
  Thomas