From: Lee Duncan <lduncan@suse.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: [PATCHv2] st: remove st_mutex
Date: Mon, 24 Sep 2012 10:16:25 -0700 [thread overview]
Message-ID: <50609569.4040304@suse.com> (raw)
In-Reply-To: <1348477560.2467.23.camel@dabdike>
On 09/24/2012 02:06 AM, James Bottomley wrote:
> On Mon, 2012-09-10 at 15:36 -0700, Lee Duncan wrote:
>> From: Hannes Reinecke <hare@suse.com>
>>
>> The st_mutex was created when the BKL was removed, and
>> prevents simultaneous st_open calls. It is better to
>> protect just the necessary data.
>>
>> Signed-off-by: Hannes Reinecke <hare@suse.com>
>> Reviewed-by: Lee Duncan <lduncan@suse.com>
>
> That should be Signed-off-by since you sent the patch to me. Signoffs
> have to follow the chain of transmission. I've assumed this was just a
> mistype.
>
> James
Thank you James.
--
Lee Duncan
prev parent reply other threads:[~2012-09-24 17:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-10 22:36 [PATCHv2] st: remove st_mutex Lee Duncan
2012-09-23 7:25 ` Kai Makisara
2012-09-24 9:06 ` James Bottomley
2012-09-24 17:16 ` Lee Duncan [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=50609569.4040304@suse.com \
--to=lduncan@suse.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=linux-scsi@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;
as well as URLs for NNTP newsgroup(s).