From: "Christopher G. Stach II" <cgs@ldsys.net>
To: linux-mips@linux-mips.org
Subject: Re: [PATCH 2.6] missing _raw_write_trylock
Date: Tue, 16 Mar 2004 13:14:25 -0600 [thread overview]
Message-ID: <1079464464.27177.12.camel@localhost> (raw)
In-Reply-To: <20040316190808.GA4944@lst.de>
CONFIG_SMP and CONFIG_PREEMPT at the same time, as it's in
kernel/sched.c.
chris
On Tue, 2004-03-16 at 13:08, Christoph Hellwig wrote:
> On Tue, Mar 16, 2004 at 09:50:00AM -0800, Jun Sun wrote:
> > > Are you going to do a non-LLSC, or are we no longer concerned about
> > > those?
> > >
> >
> > For SMP machines we assume LLSC are present. This function and its friends
> > for SMP only.
>
> doesn't CONFIG_PREEMPT (*shudder*) need it is aswell?
>
>
prev parent reply other threads:[~2004-03-16 19:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-16 15:09 [PATCH 2.6] missing _raw_write_trylock Jun Sun
2004-03-16 15:11 ` Steven J. Hill
2004-03-16 17:50 ` Jun Sun
2004-03-16 19:08 ` Christoph Hellwig
2004-03-16 19:14 ` Christopher G. Stach II [this message]
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=1079464464.27177.12.camel@localhost \
--to=cgs@ldsys.net \
--cc=linux-mips@linux-mips.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