From: Jes Sorensen <jes@trained-monkey.org>
To: Coly Li <colyli@suse.de>
Cc: linux-raid@vger.kernel.org, mariusz.tkaczyk@linux.intel.com,
pmenzel@molgen.mpg.de, Wu Guanghao <wuguanghao3@huawei.com>
Subject: Re: [PATCH v2 0/6] rebased patch set from Wu Guanghao
Date: Wed, 8 Mar 2023 13:55:53 -0500 [thread overview]
Message-ID: <a642df14-29f5-a2ec-cab8-e8db5bde1d35@trained-monkey.org> (raw)
In-Reply-To: <20230303162135.45831-1-colyli@suse.de>
On 3/3/23 11:21, Coly Li wrote:
> 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.
>
> The V2 series only changes the patch subject of mine by the suggestion
> from Paul Menzel. And nothing more changed from V1.
>
> Thank you in advance for taking them.
>
> Coly Li
All applied!
Thanks Coly rebasing these!
Jes
prev parent reply other threads:[~2023-03-08 18:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-03 16:21 [PATCH v2 0/6] rebased patch set from Wu Guanghao Coly Li
2023-03-03 16:21 ` [PATCH v2 1/6] util.c: reorder code lines in parse_layout_faulty() Coly Li
2023-03-03 16:21 ` [PATCH v2 2/6] util.c: fix memleak " Coly Li
2023-03-03 16:21 ` [PATCH v2 3/6] Detail.c: fix memleak in Detail() Coly Li
2023-03-03 16:21 ` [PATCH v2 4/6] isuper-intel.c: fix double free in load_imsm_mpb() Coly Li
2023-03-03 16:21 ` [PATCH v2 5/6] super-intel.c: fix memleak in find_disk_attached_hba() Coly Li
2023-03-03 16:21 ` [PATCH v2 6/6] super-ddf.c: fix memleak in get_vd_num_of_subarray() Coly Li
2023-03-08 18:55 ` Jes Sorensen [this message]
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=a642df14-29f5-a2ec-cab8-e8db5bde1d35@trained-monkey.org \
--to=jes@trained-monkey.org \
--cc=colyli@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=mariusz.tkaczyk@linux.intel.com \
--cc=pmenzel@molgen.mpg.de \
--cc=wuguanghao3@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 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).