From: Paul Menzel <pmenzel@molgen.mpg.de>
To: miaoguanqin@huawei.com
Cc: jes@trained-monkey.org, mariusz.tkaczyk@linux.intel.com,
linux-raid@vger.kernel.org, linfeilong@huawei.com,
lixiaokeng@huawei.com, louhongxiang@huawei.com
Subject: Re: [PATCH 1/4] Fix memory leak in file Assemble
Date: Tue, 28 Mar 2023 13:21:11 +0200 [thread overview]
Message-ID: <10ffc219-2ffc-8f0b-d18e-54d7c76ee7bc@molgen.mpg.de> (raw)
In-Reply-To: <20230323013053.3238005-2-miaoguanqin@huawei.com>
Dear Miao,
Thank you for your patches.
Am 23.03.23 um 02:30 schrieb miaoguanqin:
> When we test mdadm with asan,we found some memory leaks in Assemble.c
> We fix these memory leaks based on code logic.
>
> Signed-off-by: miaoguanqin <miaoguanqin@huawei.com>
> Signed-off-by: lixiaokeng <lixiaokeng@huawei.com>
It’d be great if you used the full names (also in your From: field)
instead of usernames. For example, Li Xiao Keng.
git config --global user.name "…"
git commit --amend --author="… <miaoguanqin@huawei.com>"
Kind regards,
Paul
next prev parent reply other threads:[~2023-03-28 11:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-23 1:30 [PATCH 0/4] Fix memory leak for Manage Assemble Kill mdadm miaoguanqin
2023-03-23 1:30 ` [PATCH 1/4] Fix memory leak in file Assemble miaoguanqin
2023-03-28 7:54 ` Mariusz Tkaczyk
2023-03-28 11:21 ` Paul Menzel [this message]
2023-03-23 1:30 ` [PATCH 2/4] Fix memory leak in file Kill miaoguanqin
2023-03-28 9:38 ` Mariusz Tkaczyk
2023-03-23 1:30 ` [PATCH 3/4] Fix memory leak in file Manage miaoguanqin
2023-03-28 10:28 ` Mariusz Tkaczyk
2023-03-23 1:30 ` [PATCH 4/4] Fix memory leak in file mdadm miaoguanqin
2023-03-28 10:29 ` Mariusz Tkaczyk
2023-04-06 11:40 [PATCH 0/4] Fix memory leak for Manage Assemble Kill mdadm Guanqin Miao
2023-04-06 11:40 ` [PATCH 1/4] Fix memory leak in file Assemble Guanqin Miao
2023-04-10 15:54 ` Jes Sorensen
2023-04-24 8:06 [PATCH 0/4] Fix memory leak for Manage Assemble Kill mdadm Guanqin Miao
2023-04-24 8:06 ` [PATCH 1/4] Fix memory leak in file Assemble Guanqin Miao
2023-08-23 13:43 ` Mariusz Tkaczyk
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=10ffc219-2ffc-8f0b-d18e-54d7c76ee7bc@molgen.mpg.de \
--to=pmenzel@molgen.mpg.de \
--cc=jes@trained-monkey.org \
--cc=linfeilong@huawei.com \
--cc=linux-raid@vger.kernel.org \
--cc=lixiaokeng@huawei.com \
--cc=louhongxiang@huawei.com \
--cc=mariusz.tkaczyk@linux.intel.com \
--cc=miaoguanqin@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.