From: Randy Dunlap <rdunlap@xenotime.net>
To: lkml <linux-kernel@vger.kernel.org>
Cc: torvalds <torvalds@linux-foundation.org>, Ingo Molnar <mingo@elte.hu>
Subject: [PATCH 6/6] sched.c: fix kernel-doc for runqueue_is_locked()
Date: Tue, 15 Mar 2011 16:12:30 -0700 [thread overview]
Message-ID: <20110315161230.c4e1e8e3.rdunlap@xenotime.net> (raw)
In-Reply-To: <20110315134316.465b6e2c.rdunlap@xenotime.net>
From: Randy Dunlap <randy.dunlap@oracle.com>
Fix kernel-doc warning for runqueue_is_locked():
Warning(kernel/sched.c:664): missing initial short description on line:
Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Ingo Molnar <mingo@elte.hu>
---
kernel/sched.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
--- lnx-2638-rc8.orig/kernel/sched.c
+++ lnx-2638-rc8/kernel/sched.c
@@ -664,10 +664,9 @@ static void update_rq_clock(struct rq *r
#endif
/**
- * runqueue_is_locked
+ * runqueue_is_locked - Returns true if the current cpu runqueue is locked
* @cpu: the processor in question.
*
- * Returns true if the current cpu runqueue is locked.
* This interface allows printk to be called with the runqueue lock
* held and know whether or not it is OK to wake up the klogd.
*/
next prev parent reply other threads:[~2011-03-15 23:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20110315134316.465b6e2c.rdunlap@xenotime.net>
2011-03-15 23:11 ` [PATCH 2/6] Documentation: add devicetree docs index file Randy Dunlap
2011-03-15 23:11 ` [PATCH 3/6] Documentation: update header filename in CodingStyle Randy Dunlap
2011-03-16 5:13 ` Harry Wei
2011-03-15 23:12 ` [PATCH 4/6] Documentation: file handles are now freed Randy Dunlap
2011-03-15 23:12 ` [PATCH 5/6] Documentation: update cgroup pid and cpuset information Randy Dunlap
2011-03-15 23:12 ` Randy Dunlap [this message]
2011-03-16 13:56 ` [tip:sched/urgent] sched, kernel-doc: Fix runqueue_is_locked() description tip-bot for Randy Dunlap
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=20110315161230.c4e1e8e3.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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®