From: Sam Ravnborg <sam@ravnborg.org>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH] kbuild: silence section mismatch warnings
Date: Sat, 12 May 2007 08:29:01 +0200 [thread overview]
Message-ID: <20070512062901.GB4073@uranus.ravnborg.org> (raw)
In-Reply-To: <8210B049-55BD-409F-8A5E-EC5E1C365604@kernel.crashing.org>
On Fri, May 11, 2007 at 04:22:28PM -0500, Kumar Gala wrote:
>
> On May 11, 2007, at 4:08 PM, Sam Ravnborg wrote:
>
> >----- Forwarded message from Sam Ravnborg <sam@ravnborg.org> -----
> >
> >Forgot lkml in first mail...
> >
> > Sam
> >
> >Subject: [RFC PATCH] kbuild: silence section mismatch warnings
> >From: Sam Ravnborg <sam@ravnborg.org>
> >Date: Fri, 11 May 2007 23:03:46 +0200
> >User-Agent: Mutt/1.4.2.1i
> >To: Chris Wedgwood <cw@f00f.org>, Andrew Morton <akpm@osdl.org>,
> > "David S. Miller" <davem@redhat.com>,
> > Russell King <rmk@arm.linux.org.uk>,
> > Satyam Sharma <satyam.sharma@gmail.com>
> >Cc: sam@ravnborg.org
> >
> >Following patch allow us in specific places to silence section
> >mismatch warnings.
> >There is a few legitime places that modpost does not yet recognize
> >where
> >reference from .text to .init.text (likewise for data) are legitime.
> >This allow us to spot the few places and annotate them so we do not
> >get false warnings that in the end will let real warnings pass.
> >
> >The annotation is simple to grep for so revieing all uses in a few
> >months time are trivial. It is assumed that a few places will
> >use this to shut up the warning as replacement for the real fix.
> >But these cases are esay to spot and to fix up.
>
> Its unclear if you expect that some things will be tagged
> __init_refok/__initdata_refok forever or if we'll find some way to
> fix/change the code so the things tagged no longer need it.
A few places will need the __init_refok tag forever.
But as Satyam points out it will likely be misused.
So the __init_refok is introduced to stay.
akpm pointed out in private mail that I need to update the
linker scripts too - and running out of time this weekend so that
will be later.
Sam
prev parent reply other threads:[~2007-05-12 6:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-11 21:08 Sam Ravnborg
2007-05-11 21:16 ` Sam Ravnborg
2007-05-11 21:22 ` Kumar Gala
2007-05-12 2:58 ` Satyam Sharma
2007-05-12 6:29 ` Sam Ravnborg [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=20070512062901.GB4073@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=galak@kernel.crashing.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®