From: Dave Jones <davej@redhat.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: smp_locks reference_discarded errors
Date: Mon, 27 Mar 2006 19:04:18 -0500 [thread overview]
Message-ID: <20060328000418.GB19025@redhat.com> (raw)
In-Reply-To: <20060326161055.GA4584@mars.ravnborg.org>
On Sun, Mar 26, 2006 at 06:10:55PM +0200, Sam Ravnborg wrote:
> Also the output from modpost provides a bit more info.
> So output from fresh -linus kernel would make it easier to locate the
> guilty stuff.
Finally coaxed latest -git to build on all archs I care about..
grab http://people.redhat.com/davej/buildlog.txt and grep for WARNING:
and see a zillion errors. The smp_locks ones seem to have disappeared
now though.
Dave
--
http://www.codemonkey.org.uk
next prev parent reply other threads:[~2006-03-28 0:04 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 [this message]
2006-03-28 0:09 ` Randy.Dunlap
2006-03-31 19:08 ` Adrian Bunk
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=20060328000418.GB19025@redhat.com \
--to=davej@redhat.com \
--cc=akpm@osdl.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