From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Stephen Boyd <sboyd@codeaurora.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>
Subject: Re: [PATCH] PM / OPP: Fix typo modifcation -> modification
Date: Fri, 25 Sep 2015 23:39:49 +0200 [thread overview]
Message-ID: <1667476.94AdzZVpPU@vostro.rjw.lan> (raw)
In-Reply-To: <CAKohpokkc-_PK1i+qVEfG4+W-jA-82T2P=w+tofWz2fYWX0NjQ@mail.gmail.com>
On Thursday, September 24, 2015 01:58:21 PM Viresh Kumar wrote:
> On 24 September 2015 at 12:28, Stephen Boyd <sboyd@codeaurora.org> wrote:
> > Reported-by: Viresh Kumar <viresh.kumar@linaro.org>
> > Signed-off-by: Stephen Boyd <sboyd@codeaurora.org>
> > ---
> > drivers/base/power/opp/core.c | 6 +++---
> > 1 file changed, 3 insertions(+), 3 deletions(-)
> >
> > diff --git a/drivers/base/power/opp/core.c b/drivers/base/power/opp/core.c
> > index 8a72f0e586e8..62b918144b5b 100644
> > --- a/drivers/base/power/opp/core.c
> > +++ b/drivers/base/power/opp/core.c
> > @@ -961,7 +961,7 @@ EXPORT_SYMBOL_GPL(dev_pm_opp_add);
> > * share a common logic which is isolated here.
> > *
> > * Return: -EINVAL for bad pointers, -ENOMEM if no memory available for the
> > - * copy operation, returns 0 if no modifcation was done OR modification was
> > + * copy operation, returns 0 if no modification was done OR modification was
> > * successful.
> > *
> > * Locking: The internal device_opp and opp structures are RCU protected.
> > @@ -1049,7 +1049,7 @@ unlock:
> > * mutex locking or synchronize_rcu() blocking calls cannot be used.
> > *
> > * Return: -EINVAL for bad pointers, -ENOMEM if no memory available for the
> > - * copy operation, returns 0 if no modifcation was done OR modification was
> > + * copy operation, returns 0 if no modification was done OR modification was
> > * successful.
> > */
> > int dev_pm_opp_enable(struct device *dev, unsigned long freq)
> > @@ -1075,7 +1075,7 @@ EXPORT_SYMBOL_GPL(dev_pm_opp_enable);
> > * mutex locking or synchronize_rcu() blocking calls cannot be used.
> > *
> > * Return: -EINVAL for bad pointers, -ENOMEM if no memory available for the
> > - * copy operation, returns 0 if no modifcation was done OR modification was
> > + * copy operation, returns 0 if no modification was done OR modification was
> > * successful.
> > */
> > int dev_pm_opp_disable(struct device *dev, unsigned long freq)
>
> Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
Applied, thanks!
Rafael
prev parent reply other threads:[~2015-09-25 21:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-24 19:28 Stephen Boyd
2015-09-24 20:58 ` Viresh Kumar
2015-09-25 21:39 ` 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=1667476.94AdzZVpPU@vostro.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=sboyd@codeaurora.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
all inboxes | Powered by JetHome®