From: Kristis Makris <mkdebian@gmx.net>
To: linux-kernel@vger.kernel.org
Subject: [PATCH] signal.c: wrong rt signals comment, 2.4.20-pre11
Date: 12 Dec 2002 22:42:40 -0700 [thread overview]
Message-ID: <1039758162.589.8.camel@mcmicro> (raw)
[-- Attachment #1: Type: text/plain, Size: 129 bytes --]
I'm sorry for being a little out of date.
I believe it's the RT signals that get queued. Someone please apply
against 2.5.x?
[-- Attachment #2: rt_signals_comment.patch --]
[-- Type: text/plain, Size: 416 bytes --]
--- linux/kernel/signal.c Sat Oct 19 11:58:48 2002
+++ linux-2.4.20-pre11.mod/kernel/signal.c Thu Dec 12 22:31:48 2002
@@ -237,7 +237,7 @@
kmem_cache_free(sigqueue_cachep,q);
atomic_dec(&nr_queued_signals);
- /* Non-RT signals can exist multiple times.. */
+ /* RT signals can exist multiple times.. */
if (sig >= SIGRTMIN) {
while ((q = *pp) != NULL) {
if (q->info.si_signo == sig)
reply other threads:[~2002-12-13 5:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1039758162.589.8.camel@mcmicro \
--to=mkdebian@gmx.net \
--cc=linux-kernel@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.