All of lore.kernel.org
 help / color / mirror / Atom feed
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	[thread overview]
Message-ID: <8501010.gC0S6gjEMf@netbook> (raw)
In-Reply-To: <50F31CB9.4010905@linaro.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

  parent reply	other threads:[~2013-01-30 20:23 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-13 19:30 [PATCH] cpuidle: fix new C-states not functional after AC disconnect Sedat Dilek
2013-01-13 20:36 ` Sedat Dilek
2013-01-13 20:44   ` Daniel Lezcano
2013-01-13 20:44     ` Daniel Lezcano
2013-01-13 20:49     ` Sedat Dilek
2013-01-30 20:23     ` Thomas Schlichter [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-01-13 12:34 Thomas Schlichter
2013-01-13 14:41 ` Daniel Lezcano
2013-01-13 14:41   ` Daniel Lezcano
2013-01-13 20:04   ` Rafael J. Wysocki
2013-01-18 20:34     ` Thomas Schlichter
2013-01-18 22:24       ` Thomas Schlichter
2013-01-31  3:52     ` Julius Werner
2013-01-31 13:21       ` Rafael J. Wysocki

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8501010.gC0S6gjEMf@netbook \
    --to=thomas.schlichter@web.de \
    --cc=daniel.lezcano@linaro.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=rjw@sisk.pl \
    --cc=sedat.dilek@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.