From: akpm@linux-foundation.org
To: oleg@redhat.com, roland@redhat.com, sukadev@us.ibm.com,
mm-commits@vger.kernel.org
Subject: [merged] signals-kill-force_sig_specific.patch removed from -mm tree
Date: Wed, 16 Dec 2009 12:38:24 -0800 [thread overview]
Message-ID: <200912162038.nBGKcO2i013424@imap1.linux-foundation.org> (raw)
The patch titled
signals: kill force_sig_specific()
has been removed from the -mm tree. Its filename was
signals-kill-force_sig_specific.patch
This patch was dropped because it was merged into mainline or a subsystem tree
The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/
------------------------------------------------------
Subject: signals: kill force_sig_specific()
From: Oleg Nesterov <oleg@redhat.com>
Kill force_sig_specific(), this trivial wrapper has no callers.
Signed-off-by: Oleg Nesterov <oleg@redhat.com>
Cc: Roland McGrath <roland@redhat.com>
Cc: Sukadev Bhattiprolu <sukadev@us.ibm.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
include/linux/sched.h | 1 -
kernel/signal.c | 6 ------
2 files changed, 7 deletions(-)
diff -puN include/linux/sched.h~signals-kill-force_sig_specific include/linux/sched.h
--- a/include/linux/sched.h~signals-kill-force_sig_specific
+++ a/include/linux/sched.h
@@ -2083,7 +2083,6 @@ extern int kill_proc_info(int, struct si
extern int do_notify_parent(struct task_struct *, int);
extern void __wake_up_parent(struct task_struct *p, struct task_struct *parent);
extern void force_sig(int, struct task_struct *);
-extern void force_sig_specific(int, struct task_struct *);
extern int send_sig(int, struct task_struct *, int);
extern void zap_other_threads(struct task_struct *p);
extern struct sigqueue *sigqueue_alloc(void);
diff -puN kernel/signal.c~signals-kill-force_sig_specific kernel/signal.c
--- a/kernel/signal.c~signals-kill-force_sig_specific
+++ a/kernel/signal.c
@@ -1062,12 +1062,6 @@ force_sig_info(int sig, struct siginfo *
return ret;
}
-void
-force_sig_specific(int sig, struct task_struct *t)
-{
- force_sig_info(sig, SEND_SIG_FORCED, t);
-}
reply other threads:[~2009-12-16 20:38 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=200912162038.nBGKcO2i013424@imap1.linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=roland@redhat.com \
--cc=sukadev@us.ibm.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 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.