From: Yang Yang <yang.yang@vivo.com>
To: Markus Elfring <Markus.Elfring@web.de>
Cc: linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org,
Jens Axboe <axboe@kernel.dk>,
onlyfever@icloud.com, linux-block@vger.kernel.org
Subject: Re: [PATCH] blk-mq: fix hang issue in blk_queue_enter()
Date: Tue, 15 Sep 2020 08:34:38 +0000 [thread overview]
Message-ID: <63816f52-4850-f586-ce73-3775ecc38da9@vivo.com> (raw)
In-Reply-To: <11a3283f-7857-0448-7424-8840fb5f2ea7@web.de>
On 2020/9/14 21:35, Markus Elfring wrote:
> …
>> The solution is to wake up the mq_freeze_wq after runtime suspend
>> completed, make blk_pm_request_resume() reexamine the q->rpm_status flag.
>
> * Would an imperative wording become helpful for the change description?
>
> * How do you think about to add the tag “Fixes” to the commit message?
>
Thank you for your suggestions.
--
Yang Yang
parent reply other threads:[~2020-09-15 8:34 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <11a3283f-7857-0448-7424-8840fb5f2ea7@web.de>]
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=63816f52-4850-f586-ce73-3775ecc38da9@vivo.com \
--to=yang.yang@vivo.com \
--cc=Markus.Elfring@web.de \
--cc=axboe@kernel.dk \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=onlyfever@icloud.com \
/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).