From: Shawn Guo <shawn.guo@linaro.org>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: rjw@rjwysocki.net, linaro-kernel@lists.linaro.org,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
arvind.chauhan@arm.com, inderpal.s@samsung.com, pavel@ucw.cz,
nm@ti.com, chander.kashyap@linaro.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Amit Daniel Kachhap <amit.daniel@samsung.com>,
Kukjin Kim <kgene.kim@samsung.com>,
Sudeep Holla <sudeep.holla@arm.com>
Subject: Re: [PATCH 0/5] CPUFreq: Initialize CPU's OPP tables from core
Date: Wed, 21 May 2014 16:59:05 +0800 [thread overview]
Message-ID: <20140521085902.GA27211@dragon> (raw)
In-Reply-To: <cover.1400480033.git.viresh.kumar@linaro.org>
On Mon, May 19, 2014 at 11:47:20AM +0530, Viresh Kumar wrote:
> Viresh Kumar (5):
...
> cpufreq: imx6q: don't initialize opp table
> cpufreq: cpufreq-cpu0: don't initialize opp table
Acked-by: Shawn Guo <shawn.guo@linaro.org>
WARNING: multiple messages have this Message-ID (diff)
From: Shawn Guo <shawn.guo@linaro.org>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: <rjw@rjwysocki.net>, <linaro-kernel@lists.linaro.org>,
<linux-pm@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<arvind.chauhan@arm.com>, <inderpal.s@samsung.com>,
<pavel@ucw.cz>, <nm@ti.com>, <chander.kashyap@linaro.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Amit Daniel Kachhap <amit.daniel@samsung.com>,
Kukjin Kim <kgene.kim@samsung.com>,
Sudeep Holla <sudeep.holla@arm.com>
Subject: Re: [PATCH 0/5] CPUFreq: Initialize CPU's OPP tables from core
Date: Wed, 21 May 2014 16:59:05 +0800 [thread overview]
Message-ID: <20140521085902.GA27211@dragon> (raw)
In-Reply-To: <cover.1400480033.git.viresh.kumar@linaro.org>
On Mon, May 19, 2014 at 11:47:20AM +0530, Viresh Kumar wrote:
> Viresh Kumar (5):
...
> cpufreq: imx6q: don't initialize opp table
> cpufreq: cpufreq-cpu0: don't initialize opp table
Acked-by: Shawn Guo <shawn.guo@linaro.org>
next prev parent reply other threads:[~2014-05-21 8:59 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-19 6:17 [PATCH 0/5] CPUFreq: Initialize CPU's OPP tables from core Viresh Kumar
2014-05-19 6:17 ` [PATCH 1/5] driver/core: cpu: initialize opp table Viresh Kumar
2014-05-19 6:29 ` [PATCH Resend] " Viresh Kumar
2014-05-19 21:13 ` Rafael J. Wysocki
2014-05-19 21:16 ` Rafael J. Wysocki
2014-05-20 2:38 ` Viresh Kumar
2014-05-20 2:38 ` Viresh Kumar
2014-05-21 23:57 ` Rafael J. Wysocki
2014-05-22 4:12 ` Viresh Kumar
2014-05-21 9:35 ` Sudeep Holla
2014-05-21 9:41 ` Viresh Kumar
2014-05-21 9:48 ` Sudeep Holla
2014-05-21 9:54 ` Viresh Kumar
2014-05-19 6:17 ` [PATCH 2/5] cpufreq: arm_big_little: don't " Viresh Kumar
2014-05-19 6:17 ` [PATCH 3/5] cpufreq: imx6q: " Viresh Kumar
2014-05-19 6:17 ` [PATCH 4/5] cpufreq: cpufreq-cpu0: " Viresh Kumar
2014-05-19 6:17 ` [PATCH 5/5] cpufreq: exynos5440: " Viresh Kumar
2014-05-21 8:59 ` Shawn Guo [this message]
2014-05-21 8:59 ` [PATCH 0/5] CPUFreq: Initialize CPU's OPP tables from core Shawn Guo
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=20140521085902.GA27211@dragon \
--to=shawn.guo@linaro.org \
--cc=amit.daniel@samsung.com \
--cc=arvind.chauhan@arm.com \
--cc=chander.kashyap@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=inderpal.s@samsung.com \
--cc=kgene.kim@samsung.com \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=nm@ti.com \
--cc=pavel@ucw.cz \
--cc=rjw@rjwysocki.net \
--cc=sudeep.holla@arm.com \
--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 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.