[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <c10ba297-c98c-5d9b-b022-5614a6986589@huawei.com>
Date: Tue, 15 Jun 2021 19:27:26 +0800
From: Zhiqiang Liu <liuzhiqiang26@...wei.com>
To: Theodore Ts'o <tytso@....edu>, Wu Guanghao <wuguanghao3@...wei.com>
CC: <linux-ext4@...r.kernel.org>,
Благодаренко Артём
<artem.blagodarenko@...il.com>, <linfeilong@...wei.com>
Subject: Re: [PATCH V2 00/12] e2fsprogs: some bugfixs and some code cleanups
friendly ping...
What is the current status of the patch set?
On 2021/5/31 12:28, 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