public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: David Miller <davem@davemloft.net>,
	cw@f00f.org, linux-kernel@vger.kernel.org
Subject: Re: (hacky) [PATCH] silence MODPOST section mismatch warnings
Date: Fri, 11 May 2007 19:57:36 +0100	[thread overview]
Message-ID: <20070511185736.GG26112@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20070511185431.GA31719@uranus.ravnborg.org>

On Fri, May 11, 2007 at 08:54:31PM +0200, Sam Ravnborg wrote:
> On Thu, May 10, 2007 at 09:54:27PM +0100, Russell King wrote:
> > On Thu, May 10, 2007 at 01:51:47PM -0700, David Miller wrote:
> > > From: Chris Wedgwood <cw@f00f.org>
> > > Date: Thu, 10 May 2007 13:34:18 -0700
> > > 
> > > > MODPOST seems to be spewing bogus warnings.  It's not clear how best
> > > > to fix it so perhaps we should silence it for now?
> > > 
> > > Most of them are legitimate, the only one that needs sorting
> > > is the mm/slab.c case and people are working on that.
> > > 
> > > The rest are useful and I've been working to fix things up
> > > on sparc64 and the networking, and in fact I'm very happy
> > > about these notifications.
> > > 
> > > Please don't apply a sledgehammer to this issue, thanks.
> > 
> > I've not had one accurate one on ARM yet.
> 
> To be able to test my modpost changes I am building arm for all configs.
> I can see a number of legitime warnings for the ARM code.
> Those I have investigated has all been of the case where functions
> are used only during init but not marked init.
> So no real bugs just potential savings and consistency.
> Shall I try to fix them up and drop you a path?

It'll probably be worth doing this after -rc1 - there's still some
stuff in flux at the moment.

However, note that my comments above were based on a mis-understanding
of the warnings.

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:

  reply	other threads:[~2007-05-11 18:57 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-10 20:34 (hacky) [PATCH] silence MODPOST section mismatch warnings Chris Wedgwood
2007-05-10 20:40 ` Russell King
2007-05-10 21:01   ` David Miller
2007-05-10 21:14   ` Sam Ravnborg
2007-05-10 20:51 ` David Miller
2007-05-10 20:54   ` Russell King
2007-05-10 21:01     ` Sam Ravnborg
2007-05-11  6:28       ` Satyam Sharma
2007-05-10 21:07     ` David Miller
2007-05-10 21:23       ` Russell King
2007-05-10 21:59       ` Russell King
2007-05-10 22:03         ` [PATCH] Make modpost section warnings clearer Russell King
2007-05-10 22:08           ` David Miller
2007-05-10 22:16         ` (hacky) [PATCH] silence MODPOST section mismatch warnings Sam Ravnborg
2007-05-10 22:18           ` Russell King
2007-05-11  4:12             ` Sam Ravnborg
2007-05-11 18:54     ` Sam Ravnborg
2007-05-11 18:57       ` Russell King [this message]
2007-05-10 21:19 ` 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=20070511185736.GG26112@flint.arm.linux.org.uk \
    --to=rmk+lkml@arm.linux.org.uk \
    --cc=cw@f00f.org \
    --cc=davem@davemloft.net \
    --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