From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Viresh Kumar <viresh.kumar@linaro.org>,
Jisheng Zhang <jszhang@marvell.com>
Cc: linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cpufreq: acpi-cpufreq: make Intel/AMD MSR access, io port access static
Date: Wed, 23 Mar 2016 22:25:06 +0100 [thread overview]
Message-ID: <22473178.Kee3EMUSMB@vostro.rjw.lan> (raw)
In-Reply-To: <20160322144353.GN5272@vireshk-i7>
On Tuesday, March 22, 2016 08:13:53 PM Viresh Kumar wrote:
> On 22-03-16, 22:34, Jisheng Zhang wrote:
> > These frequency register read/write operations' implementations for the
> > given processor (Intel/AMD MSR access or I/O port access) are only used
> > internally in acpi-cpufreq, so make them static.
> >
> > Signed-off-by: Jisheng Zhang <jszhang@marvell.com>
> > ---
> > drivers/cpufreq/acpi-cpufreq.c | 12 ++++++------
> > 1 file changed, 6 insertions(+), 6 deletions(-)
>
> Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
Applied, thanks!
prev parent reply other threads:[~2016-03-23 21:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-22 14:34 [PATCH] cpufreq: acpi-cpufreq: make Intel/AMD MSR access, io port access static Jisheng Zhang
2016-03-22 14:43 ` Viresh Kumar
2016-03-23 21:25 ` 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=22473178.Kee3EMUSMB@vostro.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=jszhang@marvell.com \
--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