mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: linaro-kernel@lists.linaro.org, patches@linaro.org,
	cpufreq@vger.kernel.org, linux-pm@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] cpufreq: fix transition_ongoing count for powernow-k8
Date: Sat, 14 Sep 2013 01:42:19 +0200	[thread overview]
Message-ID: <10372288.T6XyLE5FeS@vostro.rjw.lan> (raw)
In-Reply-To: <cover.1379062834.git.viresh.kumar@linaro.org>

On Friday, September 13, 2013 06:29:37 PM Viresh Kumar wrote:
> This has been running in my mind since few days... That we have fixed cpufreq
> core and all other drivers for transition serialization but what about
> powernow-k8? It is somewhat special (even more than exynos5440).. It queues a
> work from ->target() and may or maynot send notifications at all..
> 
> Finally I have got a solution now (detailed logs in the patch)..
> These must go with following patchset:

The "must go" here is a totally wrong way of speaking about things, because I'm
not sure I'll take this patch series yet.

> https://lkml.org/lkml/2013/9/12/173

Thanks,
Rafael


  parent reply	other threads:[~2013-09-13 23:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-13 12:59 Viresh Kumar
2013-09-13 12:59 ` [PATCH 1/2] cpufreq: Create cpufreq_transition_complete() Viresh Kumar
2013-09-13 12:59 ` [PATCH 2/2] cpufreq: powernow-k8: mark freq transition complete on error cases Viresh Kumar
2013-09-13 23:42 ` Rafael J. Wysocki [this message]
2013-09-14  4:29   ` [PATCH 0/2] cpufreq: fix transition_ongoing count for powernow-k8 Viresh Kumar

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=10372288.T6XyLE5FeS@vostro.rjw.lan \
    --to=rjw@sisk.pl \
    --cc=cpufreq@vger.kernel.org \
    --cc=linaro-kernel@lists.linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=patches@linaro.org \
    --cc=viresh.kumar@linaro.org \
    /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

all inboxes | Powered by JetHome®