From: Ralf Baechle <ralf@linux-mips.org>
To: Manish Lachwani <mlachwani@mvista.com>
Cc: linux-mips@linux-mips.org
Subject: Re: [PATCH] read_can_lock and write_can_lock for MIPS
Date: Thu, 3 Feb 2005 14:35:44 +0100 [thread overview]
Message-ID: <20050203133544.GA9688@linux-mips.org> (raw)
In-Reply-To: <20050201212603.GA24787@prometheus.mvista.com>
On Tue, Feb 01, 2005 at 01:26:03PM -0800, Manish Lachwani wrote:
> Hi Ralf,
>
> With SMP+PREEMPT, read_can_lock() and write_can_lock() need to be defined. Attached
> patch does this. Please review.
Thanks, applied. In addition I copied the comments from the i386 code
into the spinlocks.h.
Ralf
prev parent reply other threads:[~2005-02-03 13:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-01 21:26 [PATCH] read_can_lock and write_can_lock for MIPS Manish Lachwani
2005-02-03 13:35 ` Ralf Baechle [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=20050203133544.GA9688@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-mips@linux-mips.org \
--cc=mlachwani@mvista.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.