From: Andi Kleen <ak@suse.de>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] make do_signal static on i386
Date: 09 Oct 2002 10:18:49 +0200 [thread overview]
Message-ID: <p73vg4cowie.fsf@oldwotan.suse.de> (raw)
In-Reply-To: Stephen Rothwell's message of "9 Oct 2002 10:13:26 +0200"
Stephen Rothwell <sfr@canb.auug.org.au> writes:
> I am not sure whether we need the FASTCALL() or whether the change
The FASTCALL was only needed when it was still called from entry.S
(= in 2.4)
> in the comment in asm-um/signal.h makes sense. (Does UML work on
> x86_64, yet?)
I doubt that it works. At least I never tried it.
-Andi
next parent reply other threads:[~2002-10-09 8:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20021009181003.022da660.sfr@canb.auug.org.au.suse.lists.linux.kernel>
2002-10-09 8:18 ` Andi Kleen [this message]
2002-10-10 7:23 [PATCH] make do_signal static on i386 Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2002-10-09 8:10 Stephen Rothwell
2002-10-09 11:30 ` Jeff Dike
2002-10-09 17:40 ` george anzinger
2002-10-09 19:37 ` Daniel Jacobowitz
2002-10-09 20:22 ` george anzinger
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=p73vg4cowie.fsf@oldwotan.suse.de \
--to=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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