From: Sid Boyce <sboyce@blueyonder.co.uk>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.5-rc2-mm1
Date: Tue, 23 Mar 2004 01:08:11 +0000 [thread overview]
Message-ID: <405F8DFB.1010801@blueyonder.co.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 118 bytes --]
No response so far to the following.
Regards
Sid.
--
Sid Boyce .... Hamradio G3VBV and keen Flyer
Linux Only Shop.
[-- Attachment #2: Re: 2.6.5-rc2-mm1 x86_64 entry.S errors --]
[-- Type: message/rfc822, Size: 1341 bytes --]
From: Sid Boyce <sboyce@blueyonder.co.uk>
To: linux-kernel@vger.kernel.org
Subject: RE: 2.6.5-rc2-mm1 x86_64 entry.S errors
Date: Sun, 21 Mar 2004 18:24:51 +0000
Message-ID: <405DDDF3.5000609@blueyonder.co.uk>
AS arch/x86_64/kernel/entry.o
arch/x86_64/kernel/entry.S: Assembler messages:
arch/x86_64/kernel/entry.S:184: Error: missing separator
arch/x86_64/kernel/entry.S:434: Error: missing separator
arch/x86_64/kernel/entry.S:551: Error: missing separator
arch/x86_64/kernel/entry.S:554: Error: missing separator
arch/x86_64/kernel/entry.S:557: Error: missing separator
arch/x86_64/kernel/entry.S:719: Error: missing separator
arch/x86_64/kernel/entry.S:778: Error: missing separator
arch/x86_64/kernel/entry.S:806: Error: missing separator
arch/x86_64/kernel/entry.S:819: Error: missing separator
arch/x86_64/kernel/entry.S:872: Error: missing separator
arch/x86_64/kernel/entry.S:888: Error: missing separator
arch/x86_64/kernel/entry.S:912: Error: missing separator
make[1]: *** [arch/x86_64/kernel/entry.o] Error 1
make: *** [arch/x86_64/kernel] Error 2
Regards
Sid.
--
Sid Boyce .... Hamradio G3VBV and keen Flyer
Linux Only Shop.
next reply other threads:[~2004-03-23 1:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-23 1:08 Sid Boyce [this message]
2004-03-23 11:19 ` 2.6.5-rc2-mm1 Sid Boyce
2004-03-23 17:38 ` 2.6.5-rc2-mm1 Sid Boyce
-- strict thread matches above, loose matches on Subject: below --
2004-03-21 9:54 2.6.5-rc2-mm1 Andrew Morton
2004-03-21 17:40 ` 2.6.5-rc2-mm1 William Lee Irwin III
2004-03-23 2:43 ` 2.6.5-rc2-mm1 Joshua Kwan
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=405F8DFB.1010801@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.