From: Kevin Hilman <khilman@deeprootsystems.com>
To: Shawn Guo <shawn.guo@linaro.org>
Cc: "Shilimkar, Santosh" <santosh.shilimkar@ti.com>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
cpufreq@vger.kernel.org, linux-pm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] cpufreq: OMAP: remove redundant loops_per_jiffy code
Date: Thu, 06 Sep 2012 11:10:40 -0700 [thread overview]
Message-ID: <87a9x3ja3j.fsf@deeprootsystems.com> (raw)
In-Reply-To: <20120906073859.GC2362@S2101-09.ap.freescale.net> (Shawn Guo's message of "Thu, 6 Sep 2012 15:39:02 +0800")
Shawn Guo <shawn.guo@linaro.org> writes:
> On Thu, Sep 06, 2012 at 01:02:45PM +0530, Shilimkar, Santosh wrote:
>> I have acked this patch when Richard Zhao posted
>> it earlier [1]. Seems to be the same patch so ack applies
>> here as well.
>>
> Ah, I forgot Richard's patch. So Rafael, you may apply Richard's,
> since that one has been there for quite a while.
Can someone update and repost the patch from Richard with the
acks/tested-bys collected?
I will get OMAP CPUfreq patches queued for Rafael.
Kevin
WARNING: multiple messages have this Message-ID (diff)
From: khilman@deeprootsystems.com (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] cpufreq: OMAP: remove redundant loops_per_jiffy code
Date: Thu, 06 Sep 2012 11:10:40 -0700 [thread overview]
Message-ID: <87a9x3ja3j.fsf@deeprootsystems.com> (raw)
In-Reply-To: <20120906073859.GC2362@S2101-09.ap.freescale.net> (Shawn Guo's message of "Thu, 6 Sep 2012 15:39:02 +0800")
Shawn Guo <shawn.guo@linaro.org> writes:
> On Thu, Sep 06, 2012 at 01:02:45PM +0530, Shilimkar, Santosh wrote:
>> I have acked this patch when Richard Zhao posted
>> it earlier [1]. Seems to be the same patch so ack applies
>> here as well.
>>
> Ah, I forgot Richard's patch. So Rafael, you may apply Richard's,
> since that one has been there for quite a while.
Can someone update and repost the patch from Richard with the
acks/tested-bys collected?
I will get OMAP CPUfreq patches queued for Rafael.
Kevin
next prev parent reply other threads:[~2012-09-06 18:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-06 7:10 [PATCH] cpufreq: OMAP: remove redundant loops_per_jiffy code Shawn Guo
2012-09-06 7:10 ` Shawn Guo
2012-09-06 7:32 ` Shilimkar, Santosh
2012-09-06 7:32 ` Shilimkar, Santosh
2012-09-06 7:39 ` Shawn Guo
2012-09-06 7:39 ` Shawn Guo
2012-09-06 18:10 ` Kevin Hilman [this message]
2012-09-06 18:10 ` Kevin Hilman
2012-09-07 0:33 ` Shawn Guo
2012-09-07 0:33 ` 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=87a9x3ja3j.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=cpufreq@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=santosh.shilimkar@ti.com \
--cc=shawn.guo@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.