From: Randy Dunlap <rdunlap@xenotime.net>
To: linux-kernel@vger.kernel.org
Cc: Shawn Bohrer <shawn.bohrer@gmail.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Subject: [PATCH 3/6] docs: fix signal_pending argument
Date: Sun, 06 Dec 2009 18:30:44 -0800 [thread overview]
Message-ID: <12601530443872@xenotime.net> (raw)
In-Reply-To: <12601530442994@xenotime.net>
From: Shawn Bohrer <shawn.bohrer@gmail.com>
Subject: docbook: fix signal_pending() argument
Since signal_pending() takes a task_struct pointer as an argument, update
the example to pass in 'current'.
Signed-off-by: Shawn Bohrer <shawn.bohrer@gmail.com>
Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
---
Documentation/DocBook/kernel-hacking.tmpl | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- lnx-2632-rc6.orig/Documentation/DocBook/kernel-hacking.tmpl
+++ lnx-2632-rc6/Documentation/DocBook/kernel-hacking.tmpl
@@ -352,7 +352,7 @@ asmlinkage long sys_mycall(int arg)
</para>
<programlisting>
-if (signal_pending())
+if (signal_pending(current))
return -ERESTARTSYS;
</programlisting>
--
next prev parent reply other threads:[~2009-12-07 3:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-07 2:30 [PATCH 1/6 for 2.6.33] docs: use KERN_WARNING, not KERN_WARN Randy Dunlap
2009-12-07 2:30 ` [PATCH 2/6] docs: use DMA_BIT_MASK instead of inline constant Randy Dunlap
2009-12-07 2:30 ` [PATCH 5/6] docs: better explanation of procs_running Randy Dunlap
2009-12-07 2:30 ` [PATCH 6/6] docs: use misc-devices/ dir for drivers Randy Dunlap
2009-12-07 2:30 ` Randy Dunlap [this message]
2009-12-07 4:09 ` [PATCH 1/6 for 2.6.33] docs: use KERN_WARNING, not KERN_WARN Joe Perches
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=12601530443872@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=linux-kernel@vger.kernel.org \
--cc=shawn.bohrer@gmail.com \
/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