From: Matt Fleming <matt@console-pimps.org>
To: Julia Lawall <julia@diku.dk>
Cc: Paul Mundt <lethal@linux-sh.org>,
linux-sh@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH 2/2] arch/sh/mm: Eliminate a double lock
Date: Sun, 20 Jun 2010 14:51:46 +0100 [thread overview]
Message-ID: <87lja9q0b1.fsf@linux-g6p1.site> (raw)
In-Reply-To: <Pine.LNX.4.64.1006201324360.4366@ask.diku.dk>
On Sun, 20 Jun 2010 13:24:54 +0200 (CEST), Julia Lawall <julia@diku.dk> wrote:
> From: Julia Lawall <julia@diku.dk>
>
> The function begins and ends with a read_lock. The latter is changed to a
> read_unlock.
I think we've been quite lucky here so far, in that no one takes a
write_lock after we've double-read-locked pmb_rwlock.
Acked-by: Matt Fleming <matt@console-pimps.org>
next prev parent reply other threads:[~2010-06-20 13:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-20 11:24 [PATCH 2/2] arch/sh/mm: Eliminate a double lock Julia Lawall
2010-06-20 13:51 ` Matt Fleming [this message]
2010-06-21 3:58 ` Paul Mundt
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=87lja9q0b1.fsf@linux-g6p1.site \
--to=matt@console-pimps.org \
--cc=julia@diku.dk \
--cc=kernel-janitors@vger.kernel.org \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.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