public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: sedat.dilek@gmail.com
Cc: Thomas Schlichter <thomas.schlichter@web.de>,
	Linux PM List <linux-pm@lists.linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Linux ACPI <linux-acpi@vger.kernel.org>
Subject: Re: [PATCH] cpuidle: fix new C-states not functional after AC disconnect
Date: Sun, 13 Jan 2013 21:44:41 +0100	[thread overview]
Message-ID: <50F31CB9.4010905@linaro.org> (raw)
In-Reply-To: <CA+icZUUUjQTVunewhv+wEsrvyD4FsG9riHa8MRrZdMufyttA4w@mail.gmail.com>

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.

Regards.

  -- Daniel

> Have fun!
> 
> - Sedat -
> 
> On Sun, Jan 13, 2013 at 8:30 PM, Sedat Dilek <sedat.dilek@gmail.com> wrote:
>> Hi Thomas,
>>
>> I read your original LKML posting in [1].
>>
>> [ QUOTE ]
>> Currently, Daniel Lezcano seems to be working on an intrusive change of not
>> using the power_usage value at all for choosing a C-state:
>>
>> [4] https://lkml.org/lkml/2012/12/14/155
>>
>> As I could not find any of these patches in any git trees to be merged for
>> 3.8...
>> [ /QUOTE ]
>>
>> You can find the patches at LKML ([2] and [3]) or patchwork ([4] and [5]).
>>
>> As a Linux-Next "customer" I know about Daniel's work for-next [5] but
>> I did not found any other GIT repository of him.
>> Striving through Daniel's other GIT repos I found idlestat [6] and
>> powerdebug [7] tools which I want to test.
>> ( So, thank you for your email! )
>>
>> Have fun!
>>
>> Regards,
>> - Sedat -
>>
>> [0] http://marc.info/?l=linux-acpi&m=135808048905350&w=2
>> [1] https://lkml.org/lkml/2012/12/14/153
>> [2] https://lkml.org/lkml/2012/12/14/149
>> [3] https://patchwork.kernel.org/patch/1878691/
>> [4] https://patchwork.kernel.org/patch/1878701/
>> [5] http://git.linaro.org/gitweb?p=people/dlezcano/cpuidle-next.git
>> [6] http://git.linaro.org/gitweb?p=people/dlezcano/idlestat.git;a=summary
>> [7] http://git.linaro.org/gitweb?p=people/dlezcano/powerdebug.git;a=summary


-- 
 <http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs

Follow Linaro:  <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog


  reply	other threads:[~2013-01-13 20:50 UTC|newest]

Thread overview: 12+ 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 [this message]
2013-01-13 20:49     ` Sedat Dilek
2013-01-30 20:23     ` Thomas Schlichter
  -- 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 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=50F31CB9.4010905@linaro.org \
    --to=daniel.lezcano@linaro.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=sedat.dilek@gmail.com \
    --cc=thomas.schlichter@web.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox