[<prev] [next>] [day] [month] [year] [list]
Message-ID: <57045838-ae1a-d1d9-23ef-8977a4accc17@huawei.com>
Date: Mon, 31 May 2021 16:28:19 +0800
From: Wu Guanghao <wuguanghao3@...wei.com>
To: <tytso@....edu>
CC: <linux-ext4@...r.kernel.org>,
Благодаренко Артём
<artem.blagodarenko@...il.com>, <liuzhiqiang26@...wei.com>,
<linfeilong@...wei.com>
Subject: Re: [PATCH V2 00/12] e2fsprogs: some bugfixs and some code cleanups
Hello Ted,
Thank you for your advice, I will pay attention to it in the future.
Do I need to resend the series of patches
or continue to send the remaining patches this time?
Thanks,
Wu Guanghao
On Mon, 31 May 2021 00:28:46 -0400, Theodore Ts'o wrote:
>
>
>
> On Mon, May 31, 2021 at 09:23:49AM +0800, Wu Guanghao wrote:
>> V1 -> V2:
>>
>> [PATCH V2 03/12] zap_sector: fix memory leak
>> free and return operators placed in {} block
>>
>> [PATCH V2 04/12] ss_add_info_dir: fix memory leak and check whether,NULL pointer
>> modified "=" to "=="
>>
>> [PATCH V2 06/12] append_pathname: check the value returned by realloc to avoid segfault
>> [PATCH V2 07/12] argv_parse: check return value of malloc in argv_parse()
>> Fix typos
>>
>> [PATCH V2 10/12] hashmap: change return value type of, ext2fs_hashmap_add()
>> remove "new_block = NULL;"
>
> Did you only send the patches that you changed, and didn't resend the
> patches that didn't change between V1 and V2?
>
> It's actually better if you resend the whole series in the future.
>
> Thanks,
>
> - Ted
> .
> .
Powered by blists - more mailing lists