From: "David S. Miller" <davem@redhat.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: akpm@osdl.org, linux-arch@vger.kernel.org, minyard@acm.org
Subject: Re: [patch 1/8] signal handling race fix
Date: Wed, 25 Aug 2004 16:09:13 -0700 [thread overview]
Message-ID: <20040825160913.681d6868.davem@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0408251536360.17766@ppc970.osdl.org>
On Wed, 25 Aug 2004 15:40:52 -0700 (PDT)
Linus Torvalds <torvalds@osdl.org> wrote:
> I'm ok with the patch, but I _hate_ the renaming of "ka" to "ka_copy".
> There's no real point except for the initial change (to make sure the
> compiler warns about any missed entries), and once that has been done it
> just makes the patches horribly noisy and not at all more readable.
>
> As far as I can tell, the patch would be just a few lines long without
> that renaming. Can we _please_ reconsider?
I agree.
> Oh, and ia64 suddenly does the "force_sigsegv()" right, while at least the
> regular x86 port is not fixed. Shouldn't we just do the "force_sigsegv()"
> right for everybody, and put that one into kernel/signal.c?
I think this should be a seperate change and not block this one.
next prev parent reply other threads:[~2004-08-25 23:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-25 21:38 [patch 1/8] signal handling race fix akpm
2004-08-25 22:40 ` Linus Torvalds
2004-08-25 23:09 ` David S. Miller [this message]
2004-08-26 0:19 ` Linus Torvalds
2004-08-26 0:27 ` David S. Miller
2004-08-26 0:32 ` Linus Torvalds
2004-08-26 1:46 ` Linus Torvalds
2004-08-26 13:04 ` Russell King
2004-08-26 15:23 ` Linus Torvalds
2004-08-25 23:49 ` Andrew Morton
2004-08-25 23:54 ` David S. Miller
2004-08-26 0:34 ` Andrew Morton
-- strict thread matches above, loose matches on Subject: below --
2004-08-27 13:00 Martin Schwidefsky
2004-08-26 0:36 akpm
2004-08-25 21:30 akpm
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=20040825160913.681d6868.davem@redhat.com \
--to=davem@redhat.com \
--cc=akpm@osdl.org \
--cc=linux-arch@vger.kernel.org \
--cc=minyard@acm.org \
--cc=torvalds@osdl.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