From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Shailendra Verma <shailendra.capricorn@gmail.com>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cpufreq:cpufreq-nforce2 - Fix typo in comment to function nforce2_init().
Date: Tue, 16 Jun 2015 01:37:10 +0200 [thread overview]
Message-ID: <3504368.GjVHUm5yDP@vostro.rjw.lan> (raw)
In-Reply-To: <20150525072039.GA9992@linux>
On Monday, May 25, 2015 12:50:39 PM Viresh Kumar wrote:
> On 23-05-15, 10:36, Shailendra Verma wrote:
>
> Always mention something here on why this is required. Even if the
> subject is good enough :)
>
> > Signed-off-by: Shailendra Verma <shailendra.capricorn@gmail.com>
> > ---
> > drivers/cpufreq/cpufreq-nforce2.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/cpufreq/cpufreq-nforce2.c b/drivers/cpufreq/cpufreq-nforce2.c
> > index a225809..db69eeb 100644
> > --- a/drivers/cpufreq/cpufreq-nforce2.c
> > +++ b/drivers/cpufreq/cpufreq-nforce2.c
> > @@ -414,7 +414,7 @@ static int nforce2_detect_chipset(void)
> > * nforce2_init - initializes the nForce2 CPUFreq driver
> > *
> > * Initializes the nForce2 FSB support. Returns -ENODEV on unsupported
> > - * devices, -EINVAL on problems during initiatization, and zero on
> > + * devices, -EINVAL on problems during initialization, and zero on
> > * success.
> > */
> > static int __init nforce2_init(void)
>
> Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
Queued up for 4.2, thanks!
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
prev parent reply other threads:[~2015-06-15 23:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-23 5:06 [PATCH] cpufreq:cpufreq-nforce2 - Fix typo in comment to function nforce2_init() Shailendra Verma
2015-05-25 7:20 ` Viresh Kumar
2015-06-15 23:37 ` 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=3504368.GjVHUm5yDP@vostro.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=shailendra.capricorn@gmail.com \
--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