From: Adrian Bunk <bunk@stusta.de>
To: Andrew Morton <akpm@linux-foundation.org>,
trond.myklebust@fys.uio.no, davem@davemloft.net,
David Howells <dhowells@redhat.com>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: [-mm patch] fix fs/nfs/nfsroot.c compile error
Date: Sat, 5 May 2007 18:44:23 +0200 [thread overview]
Message-ID: <20070505164422.GD8975@stusta.de> (raw)
In-Reply-To: <20070505014955.8f3990b5.akpm@linux-foundation.org>
On Sat, May 05, 2007 at 01:49:55AM -0700, Andrew Morton wrote:
>...
> Changes since 2.6.21-rc7-mm2:
>...
> git-net.patch
>...
> git trees
>...
match_table_t was made "const" and gcc doesn't like "const __initdata":
<-- snip -->
...
CC fs/nfs/nfsroot.o
/home/bunk/linux/kernel-2.6/linux-2.6.21-mm1/fs/nfs/nfsroot.c:131: error: tokens causes a section type conflict
make[3]: *** [fs/nfs/nfsroot.o] Error 1
<-- snip -->
Signed-off-by: Adrian Bunk <bunk@stusta.de>
---
BTW: Why is this change to include/linux/parser.h in the net tree?
--- linux-2.6.21-mm1/fs/nfs/nfsroot.c.old 2007-05-05 18:36:26.000000000 +0200
+++ linux-2.6.21-mm1/fs/nfs/nfsroot.c 2007-05-05 18:36:44.000000000 +0200
@@ -128,7 +128,7 @@
Opt_err
};
-static match_table_t __initdata tokens = {
+static match_table_t tokens = {
{Opt_port, "port=%u"},
{Opt_rsize, "rsize=%u"},
{Opt_wsize, "wsize=%u"},
next parent reply other threads:[~2007-05-05 16:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070505014955.8f3990b5.akpm@linux-foundation.org>
2007-05-05 16:44 ` Adrian Bunk [this message]
2007-05-05 17:20 ` [-mm patch] fix fs/nfs/nfsroot.c compile error Trond Myklebust
2007-05-05 17:27 ` Trond Myklebust
2007-05-07 10:47 ` David Howells
2007-05-07 10:56 ` Adrian Bunk
2007-05-07 13:12 ` Trond Myklebust
2007-05-07 15:49 ` David Howells
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=20070505164422.GD8975@stusta.de \
--to=bunk@stusta.de \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=trond.myklebust@fys.uio.no \
/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;
as well as URLs for NNTP newsgroup(s).