From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Eric Biggers <ebiggers3@gmail.com>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cpufreq: fix comment about return value of cpufreq_register_driver()
Date: Mon, 22 Feb 2016 14:15:10 +0100 [thread overview]
Message-ID: <1933400.vKzGWdH0aj@vostro.rjw.lan> (raw)
In-Reply-To: <20160222052446.GD28226@vireshk-i7>
On Monday, February 22, 2016 10:54:46 AM Viresh Kumar wrote:
> On 20-02-16, 21:50, Eric Biggers wrote:
> > The comment has been incorrect since commit 4dea5806d332
> > ("cpufreq: return EEXIST instead of EBUSY for second registering").
> >
> > Signed-off-by: Eric Biggers <ebiggers3@gmail.com>
> > ---
> > drivers/cpufreq/cpufreq.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/cpufreq/cpufreq.c b/drivers/cpufreq/cpufreq.c
> > index e979ec7..bfefc91 100644
> > --- a/drivers/cpufreq/cpufreq.c
> > +++ b/drivers/cpufreq/cpufreq.c
> > @@ -2384,7 +2384,7 @@ EXPORT_SYMBOL_GPL(cpufreq_boost_enabled);
> > * submitted by the CPU Frequency driver.
> > *
> > * Registers a CPU Frequency driver to this core code. This code
> > - * returns zero on success, -EBUSY when another driver got here first
> > + * returns zero on success, -EEXIST when another driver got here first
> > * (and isn't unregistered in the meantime).
> > *
> > */
>
> Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
Queued up for 4.6, thanks!
prev parent reply other threads:[~2016-02-22 13:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-21 3:50 [PATCH] cpufreq: fix comment about return value of cpufreq_register_driver() Eric Biggers
2016-02-22 5:24 ` Viresh Kumar
2016-02-22 13:15 ` 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=1933400.vKzGWdH0aj@vostro.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=ebiggers3@gmail.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