public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Dave Jones <davej@redhat.com>, Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org
Subject: Re: smp_locks reference_discarded errors
Date: Fri, 31 Mar 2006 21:08:51 +0200	[thread overview]
Message-ID: <20060331190851.GB22677@stusta.de> (raw)
In-Reply-To: <20060326161055.GA4584@mars.ravnborg.org>

On Sun, Mar 26, 2006 at 06:10:55PM +0200, Sam Ravnborg wrote:
> On Sun, Mar 26, 2006 at 10:40:42AM -0500, Dave Jones wrote:
> > 
> > came out of a 'make buildcheck' a day or two ago (the following day,
> > Sam nuked reference_discarded.pl in favour of it being done
> > magically somewhere else (I've not looked into how its done now).
> The check is part of modpost now. modpost is only used when building
> modules but that holds true for most builds anyway therefore I did not
> move it to a separate executable.
>...

This doesn't sound good.

This means that we have no longer any tool that warns us about e.g. 
references from non-__exit code to __exit code [1]?

> 	Sam

cu
Adrian

[1] __exit, not __{dev,cpu,mem}exit

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  parent reply	other threads:[~2006-03-31 19:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-25  3:40 smp_locks reference_discarded errors Dave Jones
2006-03-26  7:50 ` Andrew Morton
2006-03-26 15:40   ` Dave Jones
2006-03-26 16:10     ` Sam Ravnborg
2006-03-28  0:04       ` Dave Jones
2006-03-28  0:09         ` Randy.Dunlap
2006-03-31 19:08       ` Adrian Bunk [this message]
2006-03-31 19:33         ` Sam Ravnborg
2006-03-31 23:56           ` Adrian Bunk

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=20060331190851.GB22677@stusta.de \
    --to=bunk@stusta.de \
    --cc=akpm@osdl.org \
    --cc=davej@redhat.com \
    --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