From: "Robert Schöne" <robert.schoene@tu-dresden.de>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Viresh Kumar <viresh.kumar@linaro.org>,
linaro-kernel@lists.linaro.org, linux-pm@vger.kernel.org,
prarit@redhat.com, skannan@codeaurora.org
Subject: Re: [PATCH 1/2] cpufreq: serialize calls to __cpufreq_governor()
Date: Thu, 25 Sep 2014 08:07:28 +0200 [thread overview]
Message-ID: <1411625248.18835.10.camel@x200t> (raw)
In-Reply-To: <1478598.DgG2vI5Y04@vostro.rjw.lan>
> What's the current status of this series?
>
We had some iterations of patches, but the only solution that works for
me is the patch with the coarse-grained lock that I sent at Mon, 08 Sep
2014 10:16:48 CEST [1]
Viresh is pretty occupied lately, but he told me that he might do the
tests himself when the current period of busyness is over as he is
supplied with a test system. I'm not sure about his current status (busy
or testing).
[1] http://permalink.gmane.org/gmane.linux.power-management.general/49272
--
Dipl.-Inf. Robert Schoene
Computer Scientist - R&D Energy Efficient Computing
Technische Universitaet Dresden
Center for Information Services and High Performance Computing
Distributed and Data Intensive Computing
01062 Dresden
Tel.: +49 (351) 463-42483
Fax : +49 (351) 463-37773
E-Mail: Robert.Schoene@tu-dresden.de
next prev parent reply other threads:[~2014-09-25 6:07 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-09 4:16 [PATCH 1/2] cpufreq: serialize calls to __cpufreq_governor() Viresh Kumar
2014-09-09 4:16 ` [PATCH 2/2] cpufreq: Track governor-state with 'policy->governor_state' Viresh Kumar
2014-09-09 7:29 ` [PATCH 1/2] cpufreq: serialize calls to __cpufreq_governor() Robert Schöne
2014-09-09 7:35 ` Viresh Kumar
[not found] ` <540EEA95.8030208@redhat.com>
2014-09-09 14:45 ` Viresh Kumar
2014-09-24 23:46 ` Rafael J. Wysocki
2014-09-25 6:07 ` Robert Schöne [this message]
2014-09-29 9:50 ` Viresh Kumar
2014-09-29 11:29 ` Prarit Bhargava
2014-09-29 11:38 ` Viresh Kumar
2014-09-29 11:50 ` Prarit Bhargava
2014-09-29 11:55 ` Viresh Kumar
-- strict thread matches above, loose matches on Subject: below --
2014-10-08 7:04 Viresh Kumar
2014-10-08 12:46 ` Prarit Bhargava
2014-10-10 9:04 ` Viresh Kumar
2014-10-10 10:41 ` Robert Schöne
2014-10-10 11:14 ` Viresh Kumar
2014-10-10 11:21 ` Prarit Bhargava
2014-10-10 11:30 ` Viresh Kumar
2014-10-10 11:38 ` Prarit Bhargava
2014-10-10 11:46 ` Viresh Kumar
2014-10-10 11:48 ` Prarit Bhargava
2014-10-10 12:01 ` Robert Schöne
2014-10-10 12:39 ` Viresh Kumar
2014-10-10 13:04 ` Robert Schöne
2014-10-10 13:23 ` Robert Schöne
2014-10-10 13:52 ` Viresh Kumar
2014-10-10 14:05 ` Robert Schöne
2014-10-14 6:58 ` Viresh Kumar
2014-10-14 11:42 ` Prarit Bhargava
2014-10-14 17:12 ` Prarit Bhargava
2014-10-16 10:58 ` Viresh Kumar
2014-10-17 12:12 ` Prarit Bhargava
2014-10-16 10:57 ` Viresh Kumar
2014-10-17 12:09 ` Prarit Bhargava
2014-10-10 13:40 Prarit Bhargava
2014-10-10 13:42 ` Robert Schöne
2014-10-10 13:55 Prarit Bhargava
2014-10-10 13:58 ` 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=1411625248.18835.10.camel@x200t \
--to=robert.schoene@tu-dresden.de \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-pm@vger.kernel.org \
--cc=prarit@redhat.com \
--cc=rjw@rjwysocki.net \
--cc=skannan@codeaurora.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