From mboxrd@z Thu Jan 1 00:00:00 1970 From: Zhiqiang Liu Date: Fri, 12 Jun 2020 01:01:03 +0000 Subject: Re: [PATCH V2] bcache: fix potential deadlock problem in btree_gc_coalesce Message-Id: List-Id: References: <80c2a2c6-01b9-8280-34b4-ff6b9cfaf76a@web.de> In-Reply-To: <80c2a2c6-01b9-8280-34b4-ff6b9cfaf76a@web.de> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable To: Markus Elfring , linux-bcache@vger.kernel.org Cc: linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org, Coly Li , Feilong Lin , Kent Overstreet , mingfangsen@huawei.com, renxudong1@huawei.com, Wu Bo , yanxiaodan@huawei.com Sorry for late reply. I will improve the commit log as your suggestion in v= 3 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 >=20 > * The patch version description should be placed behind triple dashes. >=20 > * I would find a shorter version identification (without the arrow) > also sufficient. >=20 >=20 >> Fixes: 2a285686c1 ("bcache: btree locking rework")> >=20 > 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/D= ocumentation/process/submitting-patches.rst?id=B2768df24ec400dd4f7fa79542f7= 97e904812053#n183 >=20 > Regards, > Markus >=20