[<prev] [next>] [day] [month] [year] [list]
Message-ID: <57fac381-20e5-ce89-7b69-1f2c576e709e@huawei.com>
Date: Wed, 19 Aug 2020 21:34:38 +0800
From: "Leizhen (ThunderTown)" <thunder.leizhen@...wei.com>
To: Markus Elfring <Markus.Elfring@....de>,
linux-nvdimm <linux-nvdimm@...ts.01.org>
CC: linux-kernel <linux-kernel@...r.kernel.org>,
Dan Williams <dan.j.williams@...el.com>,
Dave Jiang <dave.jiang@...el.com>,
Ira Weiny <ira.weiny@...el.com>,
Oliver O'Halloran <oohall@...il.com>,
Vishal Verma <vishal.l.verma@...el.com>
Subject: Re: [PATCH v2 1/4] libnvdimm: Fix memory leaks in of_pmem.c
On 8/19/2020 8:28 PM, Markus Elfring wrote:
>> The memory priv->bus_desc.provider_name allocated by kstrdup() is not
>> freed correctly.
>
> How do you think about to choose an imperative wording for
> a corresponding change description?
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?id=18445bf405cb331117bc98427b1ba6f12418ad17#n151
OK, thanks. I think I known what "imperative wording" means now.
I will rewrite the descriptions.
>
> Regards,
> Markus
>
>
Powered by blists - more mailing lists