From: Merlijn Wajer <merlijn@wizzup.org>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: linux-scsi@vger.kernel.org, Merlijn Wajer <merlijn@archive.org>,
Jens Axboe <axboe@kernel.dk>,
"James E.J. Bottomley" <jejb@linux.ibm.com>,
Arnd Bergmann <arnd@arndb.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] scsi: sr: get rid of sr global mutex
Date: Tue, 18 Feb 2020 15:41:23 +0100 [thread overview]
Message-ID: <02f9ad3c-632a-dbfe-8cca-3a8c61d77923@wizzup.org> (raw)
In-Reply-To: <yq11rqsmp2s.fsf@oracle.com>
[-- Attachment #1.1: Type: text/plain, Size: 890 bytes --]
Hi Martin,
On 18/02/2020 06:39, Martin K. Petersen wrote:
>
> Merlijn,
>
>>> When replacing the Big Kernel Lock in commit
>>> 2a48fc0ab24241755dc93bfd4f01d68efab47f5a ("block: autoconvert trivial
>>> BKL users to private mutex"), the lock was replaced with a sr-wide
>>> lock.
>>
>> Applied to 5.7/scsi-queue, thanks!
>
> Doesn't build. Please rebase on top of 5.7/scsi-queue and
> resubmit. Thanks!
I've sent out a new (v2) patch, based on `5.7/scsi-queue`. I've sent it
out using my work-email for proper attribution, and now it also matches
the Signed-off-by.
Sorry for the hassle.
One question -- I would like to put in some extra work to get this patch
(or some version of it) sent out to stable trees as well. Is there any
additional work I can do to get that going, or is it a matter of
emailing the right person/list?
Thanks,
Cheers,
Merlijn
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2020-02-18 14:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-14 13:54 [PATCH] scsi: sr: get rid of sr global mutex Merlijn Wajer
2020-02-18 5:23 ` Martin K. Petersen
2020-02-18 5:39 ` Martin K. Petersen
2020-02-18 11:17 ` Merlijn Wajer
2020-02-18 14:41 ` Merlijn Wajer [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=02f9ad3c-632a-dbfe-8cca-3a8c61d77923@wizzup.org \
--to=merlijn@wizzup.org \
--cc=arnd@arndb.de \
--cc=axboe@kernel.dk \
--cc=jejb@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=merlijn@archive.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).