From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: cpufreq@vger.kernel.org, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/9] CPUFreq Updates & Fixes for 3.10
Date: Tue, 02 Apr 2013 15:45 +0200 [thread overview]
Message-ID: <1635284.x1nGYKZPTd@vostro.rjw.lan> (raw)
In-Reply-To: <cover.1364820620.git.viresh.kumar@linaro.org>
On Monday, April 01, 2013 06:27:40 PM Viresh Kumar wrote:
> Hi Rafael,
>
> These are fixes and updates that are sent and reviewed as separate patchsets
> earlier. They are all now combined as part of a single patchset for you to apply
> in your linux-next branch.
>
> All have got reviews earlier and got fixups mailed and applied.
Whole series applied to linux-pm.git/bleeding-edge.
Thanks,
Rafael
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
prev parent reply other threads:[~2013-04-02 13:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-01 12:57 Viresh Kumar
2013-04-01 12:57 ` [PATCH 1/9] cpufreq: cpu0: Fix mistake in Documentation example Viresh Kumar
2013-04-01 12:57 ` [PATCH 2/9] cpufreq: Documentation: Fix cpufreq_frequency_table name Viresh Kumar
2013-04-01 12:57 ` [PATCH 3/9] cpufreq: cpufreq-cpu0: No need to check cpu number in init() Viresh Kumar
2013-04-01 12:57 ` [PATCH 4/9] cpufreq: cpufreq-cpu0: Call CPUFREQ_POSTCHANGE notifier for failure cases too Viresh Kumar
2013-04-01 12:57 ` [PATCH 6/9] cpufreq: Don't check if cpu is online/offline for cpufreq callbacks Viresh Kumar
2013-04-01 16:58 ` David Miller
2013-04-01 12:57 ` [PATCH 7/9] cpufreq: drivers: don't check range of target freq in .target() Viresh Kumar
2013-04-01 12:57 ` [PATCH 8/9] cpufreq: drivers: Remove unnecessary assignments of policy-> members Viresh Kumar
2013-04-01 12:57 ` [PATCH 9/9] cpufreq: ARM big LITTLE: Add generic cpufreq driver and its DT glue Viresh Kumar
2013-04-01 21:05 ` [PATCH 0/9] CPUFreq Updates & Fixes for 3.10 Rafael J. Wysocki
2013-04-02 0:43 ` Viresh Kumar
2013-04-02 12:51 ` Rafael J. Wysocki
2013-04-02 13:23 ` Viresh Kumar
2013-04-02 13:45 ` Rafael J. Wysocki [this message]
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=1635284.x1nGYKZPTd@vostro.rjw.lan \
--to=rjw@sisk.pl \
--cc=cpufreq@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.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®