linux-parisc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Grant Grundler <grundler@parisc-linux.org>
To: John David Anglin <dave@hiauly1.hia.nrc.ca>
Cc: Grant Grundler <grundler@parisc-linux.org>,
	James.Bottomley@HansenPartnership.com, kyle@mcmartin.ca,
	deller@gmx.de, linux-parisc@vger.kernel.org
Subject: Re: [PATCH][linux-2.6] Fix gcc 4.4 warning in lba_pci.c
Date: Tue, 23 Jun 2009 00:31:21 -0600	[thread overview]
Message-ID: <20090623063121.GA10963@lackof.org> (raw)
In-Reply-To: <20090621000635.6824C4FC6@hiauly1.hia.nrc.ca>

On Sat, Jun 20, 2009 at 08:06:34PM -0400, John David Anglin wrote:
> > In the meantime...if someone can explain this error I could build and test:
> > fs/nfs/nfsroot.c:400: error: __setup_str_nfs_root_setup causes a section type conflict
> > 
> > something to do with __setup(nfs_root_setup) but it's not obvious to me what.
> 
> Google says see:
> http://lkml.org/lkml/2009/5/26/329

Thank you...removing the __initconst added by this change:
-static match_table_t __initconst tokens = {
+static const match_table_t tokens __initconst = {

allows me to build. Is no one else building with NFSROOT enabled?

thanks,
grant

  reply	other threads:[~2009-06-23  6:31 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-20 22:46 [PATCH][linux-2.6] Fix gcc 4.4 warning in lba_pci.c Grant Grundler
2009-06-20 23:11 ` Grant Grundler
2009-06-20 23:26   ` James Bottomley
2009-06-20 23:29     ` Grant Grundler
2009-06-21  0:06       ` John David Anglin
2009-06-23  6:31         ` Grant Grundler [this message]
2009-06-23 11:39           ` Carlos O'Donell
2009-06-24  5:31             ` Grant Grundler
2009-06-24 13:47               ` John David Anglin
2009-06-20 23:34     ` Grant Grundler
2009-06-20 23:39       ` John David Anglin
2009-06-20 23:51         ` Grant Grundler
2009-06-20 23:55 ` [PATCH][linux-2.6] v4 : " Grant Grundler

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=20090623063121.GA10963@lackof.org \
    --to=grundler@parisc-linux.org \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=dave@hiauly1.hia.nrc.ca \
    --cc=deller@gmx.de \
    --cc=kyle@mcmartin.ca \
    --cc=linux-parisc@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 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).