From: sayli karnik <karniksayli1995@gmail.com>
To: Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 3/3] Documentation: cpu-freq: cpu-drivers: Fix repetition of word 'to'
Date: Thu, 9 Mar 2017 12:24:23 +0530 [thread overview]
Message-ID: <b186de21b6f8c7a373f577b9597d3217652c374c.1489039271.git.karniksayli1995@gmail.com> (raw)
In-Reply-To: <cover.1489039271.git.karniksayli1995@gmail.com>
The patch replaces 'to to' with 'to' in the documentation.
Signed-off-by: sayli karnik <karniksayli1995@gmail.com>
---
Documentation/cpu-freq/cpu-drivers.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/cpu-freq/cpu-drivers.txt b/Documentation/cpu-freq/cpu-drivers.txt
index f71e6be..434c49c 100644
--- a/Documentation/cpu-freq/cpu-drivers.txt
+++ b/Documentation/cpu-freq/cpu-drivers.txt
@@ -231,7 +231,7 @@ the reference implementation in drivers/cpufreq/longrun.c
Only for drivers with target_index() and CPUFREQ_ASYNC_NOTIFICATION unset.
get_intermediate should return a stable intermediate frequency platform wants to
-switch to, and target_intermediate() should set CPU to to that frequency, before
+switch to, and target_intermediate() should set CPU 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().
--
2.7.4
next prev parent reply other threads:[~2017-03-09 6:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-09 6:52 [PATCH 0/3] Fix unintentional repetition of words sayli karnik
2017-03-09 6:53 ` [PATCH 1/3] Documentation: phy: Fix repetition of word 'the' sayli karnik
2017-03-09 6:53 ` [PATCH 2/3] Documentation: ABI: testing: sysfs-bus-pci: " sayli karnik
2017-03-09 6:54 ` sayli karnik [this message]
2017-03-09 9:15 ` [PATCH 3/3] Documentation: cpu-freq: cpu-drivers: Fix repetition of word 'to' Viresh Kumar
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=b186de21b6f8c7a373f577b9597d3217652c374c.1489039271.git.karniksayli1995@gmail.com \
--to=karniksayli1995@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).