From: tip-bot for Stafford Horne <tipbot@zytor.com>
To: linux-tip-commits@vger.kernel.org
Cc: tglx@linutronix.de, torvalds@linux-foundation.org,
linux-kernel@vger.kernel.org, mingo@kernel.org, shorne@gmail.com,
hpa@zytor.com, peterz@infradead.org
Subject: [tip:sched/core] sched/wait: Fix wait_event_freezable() documentation
Date: Wed, 24 Feb 2016 21:54:31 -0800 [thread overview]
Message-ID: <tip-f4bcfa1da6fdcbc7a0854a28603bffc3c5656332@git.kernel.org> (raw)
In-Reply-To: <1456234768-24933-1-git-send-email-shorne@gmail.com>
Commit-ID: f4bcfa1da6fdcbc7a0854a28603bffc3c5656332
Gitweb: http://git.kernel.org/tip/f4bcfa1da6fdcbc7a0854a28603bffc3c5656332
Author: Stafford Horne <shorne@gmail.com>
AuthorDate: Tue, 23 Feb 2016 22:39:28 +0900
Committer: Ingo Molnar <mingo@kernel.org>
CommitDate: Wed, 24 Feb 2016 09:09:45 +0100
sched/wait: Fix wait_event_freezable() documentation
I noticed the comment label 'wait_event' was wrong.
Signed-off-by: Stafford Horne <shorne@gmail.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Thomas Gleixner <tglx@linutronix.de>
Link: http://lkml.kernel.org/r/1456234768-24933-1-git-send-email-shorne@gmail.com
Signed-off-by: Ingo Molnar <mingo@kernel.org>
---
include/linux/wait.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/linux/wait.h b/include/linux/wait.h
index ae71a76..27d7a0a 100644
--- a/include/linux/wait.h
+++ b/include/linux/wait.h
@@ -338,7 +338,7 @@ do { \
schedule(); try_to_freeze())
/**
- * wait_event - sleep (or freeze) until a condition gets true
+ * wait_event_freezable - sleep (or freeze) until a condition gets true
* @wq: the waitqueue to wait on
* @condition: a C expression for the event to wait for
*
prev parent reply other threads:[~2016-02-25 5:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-23 13:39 [PATCH] sched/wait: Fix docs on wait_event_freezable Stafford Horne
2016-02-25 5:54 ` tip-bot for Stafford Horne [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=tip-f4bcfa1da6fdcbc7a0854a28603bffc3c5656332@git.kernel.org \
--to=tipbot@zytor.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=shorne@gmail.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®