From: Eric Engestrom <eric@engestrom.ch>
To: linux-kernel@vger.kernel.org
Cc: Eric Engestrom <eric@engestrom.ch>,
Viresh Kumar <vireshk@kernel.org>, Nishanth Menon <nm@ti.com>,
Stephen Boyd <sboyd@codeaurora.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Len Brown <len.brown@intel.com>, Pavel Machek <pavel@ucw.cz>,
linux-pm@vger.kernel.org
Subject: [PATCH 31/41] Documentation: power: fix spelling mistake
Date: Mon, 25 Apr 2016 07:36:57 +0100 [thread overview]
Message-ID: <1461566229-4717-5-git-send-email-eric@engestrom.ch> (raw)
In-Reply-To: <1461566229-4717-1-git-send-email-eric@engestrom.ch>
Signed-off-by: Eric Engestrom <eric@engestrom.ch>
---
Documentation/power/opp.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/power/opp.txt b/Documentation/power/opp.txt
index c6279c2..1721a86 100644
--- a/Documentation/power/opp.txt
+++ b/Documentation/power/opp.txt
@@ -146,7 +146,7 @@ dev_pm_opp_find_freq_exact - Search for an OPP based on an *exact* frequency and
rcu_read_lock();
opp = dev_pm_opp_find_freq_exact(dev, 1000000000, false);
rcu_read_unlock();
- /* dont operate on the pointer.. just do a sanity check.. */
+ /* don't operate on the pointer.. just do a sanity check.. */
if (IS_ERR(opp)) {
pr_err("frequency not disabled!\n");
/* trigger appropriate actions.. */
--
2.8.0
next prev parent reply other threads:[~2016-04-25 6:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1461543878-3639-1-git-send-email-eric@engestrom.ch>
[not found] ` <1461543878-3639-1-git-send-email-eric-op+oiCINJLTt9jDmeYuA0g@public.gmane.org>
2016-04-25 0:24 ` [PATCH 19/41] Documentation: dt: opp: fix spelling mistake Eric Engestrom
2016-04-25 3:02 ` Viresh Kumar
2016-04-25 13:50 ` Rob Herring
[not found] ` <1461566229-4717-1-git-send-email-eric@engestrom.ch>
2016-04-25 6:36 ` Eric Engestrom [this message]
2016-04-25 6:46 ` [PATCH 31/41] Documentation: power: " 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=1461566229-4717-5-git-send-email-eric@engestrom.ch \
--to=eric@engestrom.ch \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=nm@ti.com \
--cc=pavel@ucw.cz \
--cc=rjw@rjwysocki.net \
--cc=sboyd@codeaurora.org \
--cc=vireshk@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