From: Sid Boyce <sboyce@blueyonder.co.uk>
To: linux-kernel@vger.kernel.org
Subject: 2.6.5-rc2-mm4
Date: Sun, 28 Mar 2004 03:28:15 +0100 [thread overview]
Message-ID: <4066383F.9090505@blueyonder.co.uk> (raw)
Andrew Morton wrote:
> You'll need to revert signal-race-fix.patch until the various arch guys
> catch up.
Did that, no change, looks like we have something missing in signal.c
for x86_64.
HOSTCC usr/gen_init_cpio
CPIO usr/initramfs_data.cpio
GZIP usr/initramfs_data.cpio.gz
AS usr/initramfs_data.o
LD usr/built-in.o
CC arch/x86_64/kernel/process.o
CC arch/x86_64/kernel/semaphore.o
CC arch/x86_64/kernel/signal.o
arch/x86_64/kernel/signal.c: In function `do_signal':
arch/x86_64/kernel/signal.c:426: warning: passing arg 2 of
`get_signal_to_deliver' from incompatible pointer type
arch/x86_64/kernel/signal.c:426: error: too few arguments to function
`get_signal_to_deliver'
make[1]: *** [arch/x86_64/kernel/signal.o] Error 1
make: *** [arch/x86_64/kernel] Error 2
Regards
Sid.
next reply other threads:[~2004-03-28 2:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-28 2:28 Sid Boyce [this message]
[not found] <1E741-Sh-5@gated-at.bofh.it>
2004-03-28 23:59 ` 2.6.5-rc2-mm4 Dan Hopper
2004-03-29 0:46 ` 2.6.5-rc2-mm4 Andrew Morton
2004-03-29 14:17 ` 2.6.5-rc2-mm4 Dan Hopper
-- strict thread matches above, loose matches on Subject: below --
2004-03-26 23:28 2.6.5-rc2-mm4 Sid Boyce
[not found] <4062E015.2000608@blueyonder.co.uk>
2004-03-25 19:26 ` 2.6.5-rc2-mm3 Sid Boyce
2004-03-26 23:11 ` 2.6.5-rc2-mm4 Sid Boyce
2004-03-26 23:49 ` 2.6.5-rc2-mm4 Andrew Morton
2004-03-26 21:18 2.6.5-rc2-mm4 Andrew Morton
2004-03-26 21:22 ` 2.6.5-rc2-mm4 Andrew Morton
2004-03-26 21:40 ` 2.6.5-rc2-mm4 Christoph Hellwig
2004-03-26 22:00 ` 2.6.5-rc2-mm4 Andrew Morton
2004-03-27 17:54 ` 2.6.5-rc2-mm4 Jens Axboe
2004-03-28 18:54 ` 2.6.5-rc2-mm4 Olaf Hering
2004-03-28 11:31 ` 2.6.5-rc2-mm4 Paul Mackerras
2004-03-29 15:23 ` 2.6.5-rc2-mm4 Tom Rini
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=4066383F.9090505@blueyonder.co.uk \
--to=sboyce@blueyonder.co.uk \
--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.