From: "David S. Miller" <davem@redhat.com>
To: Ricky Beam <jfbeam@bluetronic.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: kernel/signal.c rev 1.101
Date: Thu, 26 Feb 2004 14:53:03 -0800 [thread overview]
Message-ID: <20040226145303.31067b62.davem@redhat.com> (raw)
In-Reply-To: <Pine.GSO.4.33.0402261719590.28488-100000@sweetums.bluetronic.net>
On Thu, 26 Feb 2004 17:29:03 -0500 (EST)
Ricky Beam <jfbeam@bluetronic.net> wrote:
> Quote the changeset:
> ======== kernel/signal.c 1.101 ========
> D 1.101 04/02/26 03:26:02-08:00 akpm@osdl.org[torvalds] 116 115 0/3/2549
> P kernel/signal.c
> C Kill bogus __KERNEL_SYSCALLS usage
> ------------------------------------------------
>
> That's not "bogus usage" on sparc and sparc64 who's asm/signal.h requires
> __NR_restart_syscall. Removing that breaks things in a way that's very
> non-trivial to fix without touching many more files.
Actually, it is sparc's responsibility to get the right stuff wherever
it defines ptrace_signal_deliver(), which is exactly how I'm going to
fix this.
Andrew's change is correct.
prev parent reply other threads:[~2004-02-26 22:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-26 22:29 kernel/signal.c rev 1.101 Ricky Beam
2004-02-26 22:53 ` David S. Miller [this message]
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=20040226145303.31067b62.davem@redhat.com \
--to=davem@redhat.com \
--cc=jfbeam@bluetronic.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox