mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Fabio Comolli <fabio.comolli@gmail.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Section mismatch on latest git
Date: Fri, 30 May 2008 09:28:16 +0200	[thread overview]
Message-ID: <20080530072816.GA26169@uranus.ravnborg.org> (raw)
In-Reply-To: <20080529213845.d013a65e.randy.dunlap@oracle.com>

On Thu, May 29, 2008 at 09:38:45PM -0700, Randy Dunlap wrote:
> On Thu, 29 May 2008 00:01:28 -0700 Andrew Morton wrote:
> 
> > On Mon, 26 May 2008 10:03:21 +0200 "Fabio Comolli" <fabio.comolli@gmail.com> wrote:
> > 
> > > Hi.
> > > I don't know it it has been reported already:
> > > 
> > > WARNING: vmlinux.o(.text+0x114bb): Section mismatch in reference from
> > > the function nopat() to the function .cpuinit.text:pat_disable()
> > > The function nopat() references
> > > the function __cpuinit pat_disable().
> > > This is often because nopat lacks a __cpuinit
> > > annotation or the annotation of pat_disable is wrong.
> > > 
> > > Config is in attachment.
> > > 
> > 
> > This should fix it:
> > 
> > --- a/arch/x86/mm/pat.c~arch-x86-mm-patc-nopat-should-be-__init
> > +++ a/arch/x86/mm/pat.c
> > @@ -34,7 +34,7 @@ void __cpuinit pat_disable(char *reason)
> >  	printk(KERN_INFO "%s\n", reason);
> >  }
> >  
> > -static int nopat(char *str)
> > +static int __init nopat(char *str)
> >  {
> >  	pat_disable("PAT support disabled.");
> >  	return 0;
> > _
> > 
> > 
> > It turns out that this was harmless.  However it might not have been -
> > I think that adding the ability to suppress all these warnings was a
> > mistake.  
> 
> It certainly has caused me to stop looking for/at them.
> More a sin of omission than one of commission.

My plan in this area is:
- Get my dev box operational again (awaiting spare parts from Intel)
- Get usual configs warning free (or almost warning free)
- Enable the warning in kbuild-next.git right after -rc1

As my dev box is down atm I have prioritized what I conviniently
can do on my mail-box (no defconfig/all*config builds).

	Sam

  reply	other threads:[~2008-05-30  7:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-26  8:03 Fabio Comolli
2008-05-26  8:31 ` Fabio Comolli
2008-05-29  7:01 ` Andrew Morton
2008-05-30  4:38   ` Randy Dunlap
2008-05-30  7:28     ` Sam Ravnborg [this message]
2008-06-02 19:09   ` Fabio Comolli

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=20080530072816.GA26169@uranus.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=akpm@linux-foundation.org \
    --cc=fabio.comolli@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=randy.dunlap@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome