public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Frans Pop <elendil@planet.nl>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: linux-kernel@vger.kernel.org, linux-nfs@vger.kernel.org,
	parisc-linux@lists.parisc-linux.org, Helge Deller <deller@gmx.de>
Subject: Re: nfs: __setup_str_nfs_root_setup causes a section type conflict
Date: Mon, 3 Aug 2009 21:21:08 +0200	[thread overview]
Message-ID: <200908032121.10635.elendil@planet.nl> (raw)
In-Reply-To: <1249323782.18161.2.camel@heimdal.trondhjem.org>

On Monday 03 August 2009, Trond Myklebust wrote:
> > > /home/fjp/projects/kernel/linux-2.6/fs/nfs/nfsroot.c:403:
> > >     error: __setup_str_nfs_root_setup causes a section type
> > > conflict
>
> 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?

$ grep __setup_str_nfs_root_setup fs/nfs/nfsroot.i

static const char __setup_str_nfs_root_setup[] __attribute__ 
((__section__(".init.rodata"))) __attribute__((aligned(1))) = "nfsroot="; 
static struct obs_kernel_param __setup_nfs_root_setup 
__attribute__((__used__)) __attribute__ ((__section__(".init.setup"))) 
__attribute__((aligned((sizeof(long))))) = { __setup_str_nfs_root_setup, 
nfs_root_setup, 0 };

  reply	other threads:[~2009-08-03 19:21 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
2009-08-01 22:10 ` Frans Pop
2009-08-03 18:23   ` Trond Myklebust
2009-08-03 19:21     ` Frans Pop [this message]
2009-08-03 19:47       ` Trond Myklebust
2009-08-03 20:57         ` Frans Pop
2009-08-03 21:07           ` Trond Myklebust
2009-08-03 21:34             ` Frans Pop
2009-08-03 21:52             ` Sam Ravnborg
2009-08-03 22:11               ` Trond Myklebust
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=200908032121.10635.elendil@planet.nl \
    --to=elendil@planet.nl \
    --cc=deller@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=parisc-linux@lists.parisc-linux.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