From: Zhiqiang Liu <liuzhiqiang26@huawei.com>
To: Markus Elfring <Markus.Elfring@web.de>, linux-bcache@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org,
Coly Li <colyli@suse.de>, Feilong Lin <linfeilong@huawei.com>,
Kent Overstreet <kmo@daterainc.com>,
mingfangsen@huawei.com, renxudong1@huawei.com,
Wu Bo <wubo40@huawei.com>,
yanxiaodan@huawei.com
Subject: Re: [PATCH V2] bcache: fix potential deadlock problem in btree_gc_coalesce
Date: Fri, 12 Jun 2020 01:01:03 +0000 [thread overview]
Message-ID: <ae980a3c-f41b-caf6-a384-516656b6fa50@huawei.com> (raw)
In-Reply-To: <80c2a2c6-01b9-8280-34b4-ff6b9cfaf76a@web.de>
Sorry for late reply. I will improve the commit log as your suggestion in v3 patch.
Thanks for your suggestion.
On 2020/4/27 2:16, Markus Elfring wrote:
>> --
>> V1->V2: rewrite commit log (suggested by Coly Li) and rename the patch
>
> * The patch version description should be placed behind triple dashes.
>
> * I would find a shorter version identification (without the arrow)
> also sufficient.
>
>
>> Fixes: 2a285686c1 ("bcache: btree locking rework")>
>
> Will a longer commit identifier be safer for the final change description?
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?id²768df24ec400dd4f7fa79542f797e904812053#n183
>
> Regards,
> Markus
>
prev parent reply other threads:[~2020-06-12 1:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-26 18:16 [PATCH V2] bcache: fix potential deadlock problem in btree_gc_coalesce Markus Elfring
2020-06-12 1:01 ` Zhiqiang Liu [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=ae980a3c-f41b-caf6-a384-516656b6fa50@huawei.com \
--to=liuzhiqiang26@huawei.com \
--cc=Markus.Elfring@web.de \
--cc=colyli@suse.de \
--cc=kernel-janitors@vger.kernel.org \
--cc=kmo@daterainc.com \
--cc=linfeilong@huawei.com \
--cc=linux-bcache@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingfangsen@huawei.com \
--cc=renxudong1@huawei.com \
--cc=wubo40@huawei.com \
--cc=yanxiaodan@huawei.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).