From: Tom Rini <trini@kernel.crashing.org>
To: "Wojciech 'Sas' Cieciwa" <cieciwa@alpha.zarz.agh.edu.pl>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
torvalds@osdl.org, davem@redhat.com
Subject: Re: [SPARC64][PPC] strange error ..
Date: Mon, 15 Mar 2004 12:00:26 -0700 [thread overview]
Message-ID: <20040315190026.GG4342@smtp.west.cox.net> (raw)
In-Reply-To: <Pine.LNX.4.58L.0403151939460.17732@alpha.zarz.agh.edu.pl>
On Mon, Mar 15, 2004 at 07:41:57PM +0100, Wojciech 'Sas' Cieciwa wrote:
> OK. here is trivial fix:
>
> --- linux-2.6.4/init/do_mounts_initrd.c.org 2004-03-15 09:24:58.000000000 +0100
> +++ linux-2.6.4/init/do_mounts_initrd.c 2004-03-15 19:35:50.186528400 +0100
> @@ -1,6 +1,6 @@
> #define __KERNEL_SYSCALLS__
> -#include <linux/unistd.h>
> #include <linux/kernel.h>
> +#include <linux/unistd.h>
> #include <linux/fs.h>
> #include <linux/minix_fs.h>
> #include <linux/ext2_fs.h>
That leaves the more general problem of <asm/unistd.h> uses 'asmlinkage'
on platforms where either (or both) of the following can be true:
- 'asmlinkage' is a meaningless term, and shouldn't be used.
- <asm/unistd.h> doesn't include <linux/linkage.h> so it's possible
another file down the line breaks.
--
Tom Rini
http://gate.crashing.org/~trini/
next prev parent reply other threads:[~2004-03-15 19:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-15 13:41 Wojciech 'Sas' Cieciwa
2004-03-15 18:41 ` Wojciech 'Sas' Cieciwa
2004-03-15 19:00 ` Tom Rini [this message]
2004-03-15 20:39 ` David S. Miller
2004-03-15 20:43 ` Tom Rini
2004-03-15 20:54 ` Randy.Dunlap
2004-03-15 21:08 ` Tom Rini
2004-03-15 21:14 ` Randy.Dunlap
2004-03-15 21:33 ` David S. Miller
2004-03-15 22:02 ` Colin Leroy
[not found] ` <Pine.LNX.4.58L.0403160928530.23289@alpha.zarz.agh.edu.pl>
2004-03-16 15:25 ` 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=20040315190026.GG4342@smtp.west.cox.net \
--to=trini@kernel.crashing.org \
--cc=cieciwa@alpha.zarz.agh.edu.pl \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®