From: Christoph Hellwig <hch@infradead.org>
To: Joe Korty <joe.korty@ccur.com>
Cc: mingo@elte.hu, akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: Define __raw_read_lock etc for uniprocessor builds
Date: Tue, 24 Jan 2006 18:17:12 +0000 [thread overview]
Message-ID: <20060124181712.GA13277@infradead.org> (raw)
In-Reply-To: <20060124180954.GA14506@tsunami.ccur.com>
On Tue, Jan 24, 2006 at 01:09:54PM -0500, Joe Korty wrote:
>
> Make NOPed versions of __raw_read_lock and family available
> under uniprocessor kernels.
>
> Discovered when compiling a uniprocessor kernel with the
> fusyn patch applied.
>
> The standard kernel does not use __raw_read_lock etc
> outside of spinlock.c, which may account for this bug
> being undiscovered until now.
No one should call these directly. Please fix your odd patch instead.
next prev parent reply other threads:[~2006-01-24 18:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-24 18:09 Define __raw_read_lock etc for uniprocessor builds Joe Korty
2006-01-24 18:17 ` Christoph Hellwig [this message]
2006-01-24 18:29 ` Joe Korty
2006-01-24 18:32 ` Arjan van de Ven
2006-01-24 18:38 ` Joe Korty
2006-01-24 18:42 ` Arjan van de Ven
2006-01-24 18:59 ` Joe Korty
2006-01-24 21:05 ` Ingo Molnar
2006-01-24 21:12 ` Ingo Molnar
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=20060124181712.GA13277@infradead.org \
--to=hch@infradead.org \
--cc=akpm@osdl.org \
--cc=joe.korty@ccur.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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).