linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Greg KH <gregkh@suse.de>
Cc: david-b@pacbell.net, LKML <linux-kernel@vger.kernel.org>,
	len.brown@intel.com, Paul Bristow <paul@paulbristow.net>,
	mpm@selenic.com, B.Zolnierkiewicz@elka.pw.edu.pl,
	dtor_core@ameritech.net, kkeil@suse.de,
	linux-dvb-maintainer@linuxtv.org, philb@gnu.org,
	dwmw2@infradead.org
Subject: Re: kbuild: Section mismatch warnings
Date: Sun, 19 Feb 2006 01:21:33 +0100	[thread overview]
Message-ID: <20060219002133.GB11290@mars.ravnborg.org> (raw)
In-Reply-To: <20060218000921.GA15894@suse.de>

On Fri, Feb 17, 2006 at 04:09:21PM -0800, Greg KH wrote:
> On Fri, Feb 17, 2006 at 11:47:02PM +0100, Sam Ravnborg wrote:
> > Background:
> > I have introduced a build-time check for section mismatch and it showed
> > up a great number of warnings.
> > Below is the result of the run on a 2.6.16-rc1 tree (which my kbuild
> > tree is based upon) based on a 'make allmodconfig'

Greg - related to this I have thought a bit on __devinit versus __init.
With HOTPLUG enabled __devinit becomes empty and thus violate any checks
for illegal references to .init.text.

Would it make sense to create a specific set of sections for __devinit
and frinds so we could check that __devinit sections are not referenced from .text.
This is another way to do the current __init checks but with HOTPLUG
enabled and I like the result to be consistent with and without HOTPLUG
enabled.

Also I see __devinit being used in different ways. See sound/oss/mad16
for instance.
Only a few functions are marked __devinit nad I wonder if any should be
marked __devinit at all in that file. But due to references to
__initdata current checks discovered a potential bug here already today.

	Sam

  parent reply	other threads:[~2006-02-19  0:22 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-17 21:48 kbuild: Sam Ravnborg
2006-02-17 22:47 ` kbuild: Section mismatch warnings Sam Ravnborg
2006-02-17 23:32   ` Adrian Bunk
2006-02-17 23:38     ` Sam Ravnborg
2006-02-17 23:56       ` Adrian Bunk
2006-02-18  0:14       ` Nicholas Miell
2006-02-18 21:25         ` Sam Ravnborg
2006-02-18  0:09   ` Greg KH
2006-02-18  0:48     ` David Brownell
2006-02-18  0:57       ` Greg KH
2006-02-18 20:32         ` David Brownell
2006-02-19  0:21     ` Sam Ravnborg [this message]
2006-02-22  5:09       ` Greg KH
2006-02-18  0:49   ` Dmitry Torokhov
2006-02-18 12:14     ` Sam Ravnborg
2006-02-18 13:34       ` Russell King
2006-02-19 11:36   ` Sam Ravnborg
2006-02-19 12:59     ` [v4l-dvb-maintainer] " Johannes Stezenbach
2006-02-19 13:19       ` Sam Ravnborg
2006-02-19 13:30         ` Johannes Stezenbach
2006-02-25 15:31           ` Adrian Bunk
2006-02-19 14:18     ` Sam Ravnborg
2006-02-19 22:38     ` Rusty Russell
2006-02-19 22:44       ` Sam Ravnborg
2006-02-18 22:12 ` kbuild: Andi Kleen
2006-02-18 22:38   ` kbuild: Sam Ravnborg
2006-02-18 23:41     ` kbuild: 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=20060219002133.GB11290@mars.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=B.Zolnierkiewicz@elka.pw.edu.pl \
    --cc=david-b@pacbell.net \
    --cc=dtor_core@ameritech.net \
    --cc=dwmw2@infradead.org \
    --cc=gregkh@suse.de \
    --cc=kkeil@suse.de \
    --cc=len.brown@intel.com \
    --cc=linux-dvb-maintainer@linuxtv.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mpm@selenic.com \
    --cc=paul@paulbristow.net \
    --cc=philb@gnu.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).