From: Bart Van Assche <bart.vanassche@wdc.com>
To: "jianchao.wang" <jianchao.w.wang@oracle.com>,
"axboe@kernel.dk" <axboe@kernel.dk>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: Re: [PATCH] blk-mq: use mutex_trylock to avoid lock inversion
Date: Tue, 26 Jun 2018 08:36:53 -0700 [thread overview]
Message-ID: <1d4d1dc3-7014-4e2a-1ea5-e1446381b404@wdc.com> (raw)
In-Reply-To: <a0350d07-3c11-c04c-d9ba-94a5868e7d8f@oracle.com>
On 06/25/18 20:47, jianchao.wang wrote:
> V2 patch has been posted, would you please take a look at on them ?
> https://marc.info/?l=linux-block&m=152965143412927&w=2
Hello Jianchao,
Patches 1/3 and 2/3 of that series look fine to me but I don't like the
approach of patch 3/3 so please do not expect a review from me for that
patch.
Thanks,
Bart.
next prev parent reply other threads:[~2018-06-26 15:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-19 7:00 [PATCH] blk-mq: use mutex_trylock to avoid lock inversion Jianchao Wang
2018-06-19 15:20 ` Bart Van Assche
2018-06-20 2:09 ` jianchao.wang
2018-06-20 16:18 ` Bart Van Assche
2018-06-21 8:23 ` jianchao.wang
2018-06-26 3:46 ` jianchao.wang
2018-06-26 15:36 ` Bart Van Assche [this message]
2018-06-28 1:11 ` jianchao.wang
2018-06-28 1:15 ` jianchao.wang
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=1d4d1dc3-7014-4e2a-1ea5-e1446381b404@wdc.com \
--to=bart.vanassche@wdc.com \
--cc=axboe@kernel.dk \
--cc=jianchao.w.wang@oracle.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@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