mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kumar Gala <galak@kernel.crashing.org>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH] kbuild: silence section mismatch warnings
Date: Fri, 11 May 2007 16:22:28 -0500	[thread overview]
Message-ID: <8210B049-55BD-409F-8A5E-EC5E1C365604@kernel.crashing.org> (raw)
In-Reply-To: <20070511210850.GA382@uranus.ravnborg.org>


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.

> With this and the following two patches I have a section mismatch free
> build.
> The plan is that a section mismatch soon will graduate from a  
> warning to an error.
> This will hurt a few drives but then they have an incentive to fix  
> it up.
>
> Comments welcome.

- k

  parent reply	other threads:[~2007-05-11 21:22 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 [this message]
2007-05-12  2:58   ` Satyam Sharma
2007-05-12  6:29   ` Sam Ravnborg

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=8210B049-55BD-409F-8A5E-EC5E1C365604@kernel.crashing.org \
    --to=galak@kernel.crashing.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

all inboxes | Powered by JetHome®