From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Viresh Kumar <viresh.kumar@linaro.org>,
Steve Muckle <steve.muckle@linaro.org>
Cc: "Rafael J . Wysocki" <rafael@kernel.org>,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
Stephen Rothwell <sfr@canb.auug.org.au>,
Steve Muckle <smuckle@linaro.org>
Subject: Re: [PATCH] cpufreq: export cpufreq_driver_resolve_freq()
Date: Fri, 22 Jul 2016 14:05:08 +0200 [thread overview]
Message-ID: <1725760.m6ucNt3ELb@vostro.rjw.lan> (raw)
In-Reply-To: <20160722033044.GO3122@ubuntu>
On Thursday, July 21, 2016 08:30:44 PM Viresh Kumar wrote:
> On 21-07-16, 19:24, Steve Muckle wrote:
> > Export cpufreq_driver_resolve_freq() since governors may be compiled as
> > modules.
> >
> > Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>
> > Signed-off-by: Steve Muckle <smuckle@linaro.org>
> > ---
> > drivers/cpufreq/cpufreq.c | 1 +
> > 1 file changed, 1 insertion(+)
> >
> > diff --git a/drivers/cpufreq/cpufreq.c b/drivers/cpufreq/cpufreq.c
> > index b696baeb249d..fa0a92d6121e 100644
> > --- a/drivers/cpufreq/cpufreq.c
> > +++ b/drivers/cpufreq/cpufreq.c
> > @@ -514,6 +514,7 @@ unsigned int cpufreq_driver_resolve_freq(struct cpufreq_policy *policy,
> > CPUFREQ_RELATION_L);
> > return policy->freq_table[policy->cached_resolved_idx].frequency;
> > }
> > +EXPORT_SYMBOL_GPL(cpufreq_driver_resolve_freq);
> >
> > /*********************************************************************
> > * SYSFS INTERFACE *
>
> Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
Applied (after a bit of rebasing).
Thanks,
Rafael
prev parent reply other threads:[~2016-07-22 12:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-22 2:24 [PATCH] cpufreq: export cpufreq_driver_resolve_freq() Steve Muckle
2016-07-22 3:30 ` Viresh Kumar
2016-07-22 12:05 ` 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=1725760.m6ucNt3ELb@vostro.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=smuckle@linaro.org \
--cc=steve.muckle@linaro.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