From: "Steven J. Hill" <sjhill@realitydiluted.com>
To: Jun Sun <jsun@mvista.com>
Cc: linux-mips@linux-mips.org
Subject: Re: [PATCH 2.6] missing _raw_write_trylock
Date: Tue, 16 Mar 2004 10:11:18 -0500 [thread overview]
Message-ID: <40571916.6060502@realitydiluted.com> (raw)
In-Reply-To: <20040316070911.B29232@mvista.com>
Jun Sun wrote:
> Please help me reviewing the code, because inline assembly bug is
> always tricky and miserable.
>
Are you going to do a non-LLSC, or are we no longer concerned about
those?
-Steve
next prev parent reply other threads:[~2004-03-16 15:11 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 [this message]
2004-03-16 17:50 ` Jun Sun
2004-03-16 19:08 ` Christoph Hellwig
2004-03-16 19:14 ` Christopher G. Stach II
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=40571916.6060502@realitydiluted.com \
--to=sjhill@realitydiluted.com \
--cc=jsun@mvista.com \
--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