linux-kernel - [tip:sched/urgent] sched: Fix yield

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Sat, 19 Mar 2011 18:22:22 GMT
From:	tip-bot for Randy Dunlap <randy.dunlap@...cle.com>
To:	linux-tip-commits@...r.kernel.org
Cc:	linux-kernel@...r.kernel.org, hpa@...or.com, mingo@...hat.com,
	peterz@...radead.org, tglx@...utronix.de, randy.dunlap@...cle.com,
	mingo@...e.hu
Subject: [tip:sched/urgent] sched: Fix yield_to kernel-doc

Commit-ID:  16addf954d3954a72fd56abc02ffcba3c18529a1
Gitweb:     http://git.kernel.org/tip/16addf954d3954a72fd56abc02ffcba3c18529a1
Author:     Randy Dunlap <randy.dunlap@...cle.com>
AuthorDate: Fri, 18 Mar 2011 09:34:53 -0700
Committer:  Ingo Molnar <mingo@...e.hu>
CommitDate: Sat, 19 Mar 2011 19:19:36 +0100

sched: Fix yield_to kernel-doc

Add missing function parameters for yield_to():

 Warning(kernel/sched.c:5470): No description found for parameter 'p'
 Warning(kernel/sched.c:5470): No description found for parameter 'preempt'

Signed-off-by: Randy Dunlap <randy.dunlap@...cle.com>
Cc: Peter Zijlstra <peterz@...radead.org>
LKML-Reference: <20110318093453.8f7489a4.randy.dunlap@...cle.com>
Signed-off-by: Ingo Molnar <mingo@...e.hu>
---
 kernel/sched.c |    2 ++
 1 files changed, 2 insertions(+), 0 deletions(-)

diff --git a/kernel/sched.c b/kernel/sched.c
index 58d66ea..052120d 100644
--- a/kernel/sched.c
+++ b/kernel/sched.c
@@ -5467,6 +5467,8 @@ EXPORT_SYMBOL(yield);
  * yield_to - yield the current processor to another thread in
  * your thread group, or accelerate that thread toward the
  * processor it's on.
+ * @p: target task
+ * @preempt: whether task preemption is allowed or not
  *
  * It's the caller's job to ensure that the target task struct
  * can't go away on us before we can do any checks.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/