From: "Rafael J. Wysocki" <rafael@kernel.org>
To: Wang Wenhu <wenhu.wang@vivo.com>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Viresh Kumar <viresh.kumar@linaro.org>,
Linux PM <linux-pm@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
kernel@vivo.com
Subject: Re: [PATCH] cpufreq: fix a minor typo for cpufreq_driver doc
Date: Thu, 14 May 2020 13:43:04 +0200 [thread overview]
Message-ID: <CAJZ5v0jHVMA5=fYkDqSLdpvxFi8iHvxVa-ZkT71cbd4hr1ohDg@mail.gmail.com> (raw)
In-Reply-To: <20200513141854.18451-1-wenhu.wang@vivo.com>
On Wed, May 13, 2020 at 4:26 PM Wang Wenhu <wenhu.wang@vivo.com> wrote:
>
> Delete the duplicate "to" possibly double-typed.
>
> Signed-off-by: Wang Wenhu <wenhu.wang@vivo.com>
> Cc: Viresh Kumar <viresh.kumar@linaro.org>
> ---
> include/linux/cpufreq.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/include/linux/cpufreq.h b/include/linux/cpufreq.h
> index f7240251a949..67d5950bd878 100644
> --- a/include/linux/cpufreq.h
> +++ b/include/linux/cpufreq.h
> @@ -330,7 +330,7 @@ struct cpufreq_driver {
> *
> * get_intermediate should return a stable intermediate frequency
> * platform wants to switch to and target_intermediate() should set CPU
> - * to to that frequency, before jumping to the frequency corresponding
> + * to that frequency, before jumping to the frequency corresponding
> * to 'index'. Core will take care of sending notifications and driver
> * doesn't have to handle them in target_intermediate() or
> * target_index().
> --
Applied as 5.8 material with some minor subject changes, thanks!
prev parent reply other threads:[~2020-05-14 11:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-13 14:18 [PATCH] cpufreq: fix a minor typo for cpufreq_driver doc Wang Wenhu
2020-05-14 11:43 ` 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='CAJZ5v0jHVMA5=fYkDqSLdpvxFi8iHvxVa-ZkT71cbd4hr1ohDg@mail.gmail.com' \
--to=rafael@kernel.org \
--cc=kernel@vivo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=viresh.kumar@linaro.org \
--cc=wenhu.wang@vivo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).