All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Drake <dsd@gentoo.org>
To: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Richard Henderson <rth@twiddle.net>,
	tony.luck@intel.com, anton@samba.org, paulus@samba.org,
	Adrian Bunk <bunk@kernel.org>,
	Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>,
	rusty@rustcorp.com.au, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] moduleparam: fix alpha, ia64 and ppc64 compile failures
Date: Sat, 09 Feb 2008 16:50:49 +0000	[thread overview]
Message-ID: <47ADD9E9.8090908@gentoo.org> (raw)
In-Reply-To: <20080208223341.GB15333@jurassic.park.msu.ru>

Ivan Kokshaysky wrote:
> On alpha, ia64 and ppc64 only relocations to local data can go into
> read-only sections. The vast majority of module parameters use the global
> generic param_set_*/param_get_* functions, so the 'const' attribute for
> struct kernel_param is not only useless, but it also causes compile
> failures due to 'section type conflict' in those rare cases where
> param_set/get are local functions.
> 
> This fixes http://bugzilla.kernel.org/show_bug.cgi?id=8964

In case you weren't aware already, people seem to think this is actually 
a GCC bug (with a patch available):

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31490

Daniel


      parent reply	other threads:[~2008-02-09 16:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-08 22:33 [PATCH] moduleparam: fix alpha, ia64 and ppc64 compile failures Ivan Kokshaysky
2008-02-08 22:46 ` Andrew Morton
2008-02-08 23:35   ` Ivan Kokshaysky
2008-02-09 16:50 ` Daniel Drake [this message]

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=47ADD9E9.8090908@gentoo.org \
    --to=dsd@gentoo.org \
    --cc=akpm@linux-foundation.org \
    --cc=anton@samba.org \
    --cc=bunk@kernel.org \
    --cc=ink@jurassic.park.msu.ru \
    --cc=kamalesh@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulus@samba.org \
    --cc=rth@twiddle.net \
    --cc=rusty@rustcorp.com.au \
    --cc=tony.luck@intel.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.