From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Frans Pop <elendil-EIBgga6/0yRmR6Xm/wNWPw@public.gmane.org>
Cc: linux-kernel@vger.kernel.org, linux-nfs@vger.kernel.org,
parisc-linux-T/XaZq8tFt7U4lJK3ijXoz+iFHGzDt/a@public.gmane.org,
Helge Deller <deller@gmx.de>
Subject: Re: nfs: __setup_str_nfs_root_setup causes a section type conflict
Date: Mon, 03 Aug 2009 14:23:02 -0400 [thread overview]
Message-ID: <1249323782.18161.2.camel@heimdal.trondhjem.org> (raw)
In-Reply-To: <200908020010.30459.elendil-EIBgga6/0yRmR6Xm/wNWPw@public.gmane.org>
On Sun, 2009-08-02 at 00:10 +0200, Frans Pop wrote:
> On Friday 31 July 2009, Frans Pop wrote:
> > While compiling v2.6.31-rc4-294-gf5886c7 for parisc (64-bits) I ran
> > into the following compilation error:
> >
> > /home/fjp/projects/kernel/linux-2.6/fs/nfs/nfsroot.c:403:
> > error: __setup_str_nfs_root_setup causes a section type conflict
> > make[7]: *** [fs/nfs/nfsroot.o] Error 1
>
If you do a 'make fs/nfs/nfsroot.i', and then look at the resulting file
fs/nfs/nfsroot.i, what does the line that defines
'__setup_str_nfs_root_setup' look like?
Cheers
Trond
next prev parent reply other threads:[~2009-08-03 18:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-31 12:46 nfs: __setup_str_nfs_root_setup causes a section type conflict Frans Pop
[not found] ` <200907311446.33486.elendil-EIBgga6/0yRmR6Xm/wNWPw@public.gmane.org>
2009-08-01 22:10 ` Frans Pop
[not found] ` <200908020010.30459.elendil-EIBgga6/0yRmR6Xm/wNWPw@public.gmane.org>
2009-08-03 18:23 ` Trond Myklebust [this message]
[not found] ` <1249323782.18161.2.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2009-08-03 19:21 ` Frans Pop
2009-08-03 19:47 ` Trond Myklebust
2009-08-03 20:57 ` Frans Pop
[not found] ` <200908032257.51739.elendil-EIBgga6/0yRmR6Xm/wNWPw@public.gmane.org>
2009-08-03 21:07 ` Trond Myklebust
[not found] ` <1249333643.18161.36.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2009-08-03 21:34 ` Frans Pop
2009-08-03 21:52 ` Sam Ravnborg
[not found] ` <20090803215237.GA956-OoSGOWW0KRunlFQ6Q1D1Y0B+6BGkLq7r@public.gmane.org>
2009-08-03 22:11 ` Trond Myklebust
[not found] ` <1249337493.18161.52.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2009-08-05 19:47 ` Helge Deller
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=1249323782.18161.2.camel@heimdal.trondhjem.org \
--to=trond.myklebust@fys.uio.no \
--cc=deller@gmx.de \
--cc=elendil-EIBgga6/0yRmR6Xm/wNWPw@public.gmane.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=parisc-linux-T/XaZq8tFt7U4lJK3ijXoz+iFHGzDt/a@public.gmane.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