From: Andrew Morton <akpm@linux-foundation.org>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: linux-kernel@vger.kernel.org, jeff@garzik.org
Subject: Re: - typhoon-section-fix.patch removed from -mm tree
Date: Thu, 7 Feb 2008 15:03:32 -0800 [thread overview]
Message-ID: <20080207150332.ecf6b756.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080207223601.GB23004@uranus.ravnborg.org>
On Thu, 7 Feb 2008 23:36:01 +0100
Sam Ravnborg <sam@ravnborg.org> wrote:
> On Thu, Feb 07, 2008 at 02:30:08PM -0800, akpm@linux-foundation.org wrote:
> >
> > The patch titled
> > typhoon section fix
> > has been removed from the -mm tree. Its filename was
> > typhoon-section-fix.patch
> >
> > This patch was dropped because I just remembered __devexitconst :(
>
> But powerpc is subtle and I foresee that we have to kill __devinitconst
> and friends soonish.
> The problem is that despite data being const the compiler does not
> always mark the section const.
> So we will see a lot of the errors you see for powerpc now
> that we unconditionally specify a section.
>
> Previously this inconsistentcy were hidden by the fact that powerpc tagets
> seldom were build without CONFIG_HOTPLUG=y.
>
> So the patches are correct.
> Tomorrow I hope to do a patch that kill __devinitconst :-(
>
hrm, OK.
> >
> > -static const char version[] __devinitdata =
> > +static char version[] __devinitdata =
> > "typhoon.c: version " DRV_MODULE_VERSION " (" DRV_MODULE_RELDATE ")\n";
> >
but chances are that in a year's time someone will come along and helpfully
make this const again. Maybe we should annotate such sites with
#define cant_make_me_const_ask_sam_why /**/
to avoid this..
prev parent reply other threads:[~2008-02-07 23:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200802072230.m17MU87x025986@imap1.linux-foundation.org>
2008-02-07 22:36 ` - typhoon-section-fix.patch removed from -mm tree Sam Ravnborg
2008-02-07 23:03 ` Andrew Morton [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=20080207150332.ecf6b756.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.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