From: Paul Mundt <lethal@linux-sh.org>
To: Julia Lawall <julia@diku.dk>
Cc: 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: Mon, 21 Jun 2010 03:58:10 +0000 [thread overview]
Message-ID: <20100621035809.GB29997@linux-sh.org> (raw)
In-Reply-To: <Pine.LNX.4.64.1006201324360.4366@ask.diku.dk>
On Sun, Jun 20, 2010 at 01:24:54PM +0200, Julia Lawall wrote:
> From: Julia Lawall <julia@diku.dk>
>
> The function begins and ends with a read_lock. The latter is changed to a
> read_unlock.
>
Indeed, good catch. Applied, thanks.
WARNING: multiple messages have this Message-ID (diff)
From: Paul Mundt <lethal@linux-sh.org>
To: Julia Lawall <julia@diku.dk>
Cc: 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: Mon, 21 Jun 2010 12:58:10 +0900 [thread overview]
Message-ID: <20100621035809.GB29997@linux-sh.org> (raw)
In-Reply-To: <Pine.LNX.4.64.1006201324360.4366@ask.diku.dk>
On Sun, Jun 20, 2010 at 01:24:54PM +0200, Julia Lawall wrote:
> From: Julia Lawall <julia@diku.dk>
>
> The function begins and ends with a read_lock. The latter is changed to a
> read_unlock.
>
Indeed, good catch. Applied, thanks.
next prev parent reply other threads:[~2010-06-21 3:58 UTC|newest]
Thread overview: 6+ 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 11:24 ` Julia Lawall
2010-06-20 13:51 ` Matt Fleming
2010-06-20 13:51 ` Matt Fleming
2010-06-21 3:58 ` Paul Mundt [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=20100621035809.GB29997@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=julia@diku.dk \
--cc=kernel-janitors@vger.kernel.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 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.