From: Viresh Kumar <viresh.kumar@linaro.org>
To: Shailendra Verma <shailendra.capricorn@gmail.com>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
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: Mon, 25 May 2015 12:50:39 +0530 [thread overview]
Message-ID: <20150525072039.GA9992@linux> (raw)
In-Reply-To: <1432357578-4069-1-git-send-email-shailendra.capricorn@gmail.com>
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>
--
viresh
next prev parent reply other threads:[~2015-05-25 7:20 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 [this message]
2015-06-15 23:37 ` Rafael J. Wysocki
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=20150525072039.GA9992@linux \
--to=viresh.kumar@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=shailendra.capricorn@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.