From: Jes Sorensen <jes@trained-monkey.org>
To: Coly Li <colyli@suse.de>
Cc: Mateusz Kusiak <mateusz.kusiak@intel.com>, linux-raid@vger.kernel.org
Subject: Re: [PATCH v3] Grow: Split Grow_reshape into helper function
Date: Mon, 15 Aug 2022 15:18:31 -0400 [thread overview]
Message-ID: <fab92bc5-b9c1-22a0-4ea0-41cd1d952b65@trained-monkey.org> (raw)
In-Reply-To: <2622AABD-75DC-41D4-9F1E-E958463E9FD0@suse.de>
On 8/8/22 06:03, Coly Li wrote:
>
>
>> 2022年8月8日 04:41,Jes Sorensen <jes@trained-monkey.org> 写道:
>>
>> On 6/9/22 03:41, Mateusz Kusiak wrote:
>>> Grow_reshape should be split into helper functions given its size.
>>> - Add helper function for preparing reshape on external metadata.
>>> - Close cfd file descriptor.
>>> Signed-off-by: Mateusz Kusiak <mateusz.kusiak@intel.com>
>>> ---
>>> Changes since v2:
>>> - removed dot from commit message
>>> - formatted commit description as a list
>>> - got rid of returning -1 in prepare_external_reshape()
>>> - changed "return" section in prepare_external_reshape() description
>>
>> Hi Mateusz,
>>
>> Changes look good to me, but it no longer applies. Mind sending an updated version?
>
> Hi Jes,
>
> Please check the version I post to you in series “mdadm-CI for-jes/20220728: patches for merge” (Message-Id: <20220728122101.28744-1-colyli@suse.de>), the patch in this series is rebased and confirmed with Mateusz, it could be applied to upstream mdadm.
Hi Coly,
It is really painful for me to pull individual patches out of a large
set like that. It is much easier to deal with acks and updated patches
and being able to pull in smaller sets via patchworks.
Thanks,
Jes
next prev parent reply other threads:[~2022-08-15 21:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-09 7:41 [PATCH v3] Grow: Split Grow_reshape into helper function Mateusz Kusiak
2022-06-20 17:21 ` Coly Li
2022-06-28 15:56 ` Coly Li
2022-06-29 13:12 ` Kusiak, Mateusz
2022-06-29 13:14 ` Coly Li
2022-08-07 20:41 ` Jes Sorensen
2022-08-08 10:03 ` Coly Li
2022-08-15 19:18 ` Jes Sorensen [this message]
2022-08-24 15:56 ` Jes Sorensen
2022-08-24 16:09 ` Coly Li
2022-08-24 16:33 ` Jes Sorensen
2022-08-24 16:41 ` 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=fab92bc5-b9c1-22a0-4ea0-41cd1d952b65@trained-monkey.org \
--to=jes@trained-monkey.org \
--cc=colyli@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=mateusz.kusiak@intel.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.