From: Coly Li <colyli@suse.de>
To: jes@trained-monkey.org
Cc: linux-raid@vger.kernel.org, Coly Li <colyli@suse.de>
Subject: [PATCH 0/6] rebased patch set from Wu Guanghao
Date: Fri, 3 Mar 2023 16:33:17 +0800 [thread overview]
Message-ID: <20230303083323.3406-1-colyli@suse.de> (raw)
Hi Jes,
This is the rebased patch set from Wu Guanghao, all the patches can
be applied on top of commit 0a07dea8d3b78 ("Mdmonitor: Refactor
check_one_sharer() for better error handling") from the mdadm tree.
The patch from me is to solve conflict for the first patch of Guanghao.
In order to make the commit logs to be more understandable, I recompose
some patch subjects or commit logs.
Thank you in advance for taking them.
Coly Li
---
Coly Li (1):
util.c: code cleanup for parse_layout_faulty()
Wu Guanghao (5):
util.c: fix memleak in parse_layout_faulty()
Detail.c: fix memleak in Detail()
isuper-intel.c: fix double free in load_imsm_mpb()
super-intel.c: fix memleak in find_disk_attached_hba()
super-ddf.c: fix memleak in get_vd_num_of_subarray()
Detail.c | 1 +
super-ddf.c | 9 +++++++--
super-intel.c | 5 +++--
util.c | 11 ++++++++---
4 files changed, 19 insertions(+), 7 deletions(-)
--
2.39.2
next reply other threads:[~2023-03-03 8:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-03 8:33 Coly Li [this message]
2023-03-03 8:33 ` [PATCH 1/6] util.c: code cleanup for parse_layout_faulty() Coly Li
2023-03-03 10:22 ` Paul Menzel
2023-03-03 8:33 ` [PATCH 2/6] util.c: fix memleak in parse_layout_faulty() Coly Li
2023-03-03 8:33 ` [PATCH 3/6] Detail.c: fix memleak in Detail() Coly Li
2023-03-03 8:33 ` [PATCH 4/6] isuper-intel.c: fix double free in load_imsm_mpb() Coly Li
2023-03-03 8:33 ` [PATCH 5/6] super-intel.c: fix memleak in find_disk_attached_hba() Coly Li
2023-03-03 8:33 ` [PATCH 6/6] super-ddf.c: fix memleak in get_vd_num_of_subarray() Coly Li
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=20230303083323.3406-1-colyli@suse.de \
--to=colyli@suse.de \
--cc=jes@trained-monkey.org \
--cc=linux-raid@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).