All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Kusiak, Mateusz" <mateusz.kusiak@linux.intel.com>
To: Coly Li <colyli@suse.de>, Mateusz Kusiak <mateusz.kusiak@intel.com>
Cc: linux-raid <linux-raid@vger.kernel.org>, jes@trained-monkey.org
Subject: Re: [PATCH v3] Grow: Split Grow_reshape into helper function
Date: Wed, 29 Jun 2022 15:12:05 +0200	[thread overview]
Message-ID: <43497f54-7b9f-7ad3-b965-b9f83a3fbed3@linux.intel.com> (raw)
In-Reply-To: <702B9063-D708-451A-A8F2-6DFD77728B9B@suse.de>

On 28/06/2022 17:56, Coly Li wrote:
> 
> 
>> 2022年6月21日 01:21,Coly Li <colyli@suse.de> 写道:
>>
>>
>>
>>> 2022年6月9日 15:41,Mateusz Kusiak <mateusz.kusiak@intel.com> 写道:
>>>
>>> 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>
>>
>> Hi Mateusz,
>>
>> Overall I am fine with this patch. Currently it dose apply on branch 20220621-testing of the mdadm-CI tree. This branch is based on mdadm upstream commit 756a15f32338 (“imsm: Remove possibility for get_imsm_dev to return NULL”) and stacked with other asked patch from for-jes/20220620.
>>
>> I will response this patch after other queuing patches are handled by Jes. If the change is minor, I will do the patch rebase and inform you.
> 
> Hi Mateusz,
> 
> I just rebased the patch and pushed to mdadm-CI tree into branch 20220621-testing. This is the only patch in this testing branch. It looks fine to me, but can you help to confirm whether the rebase is correctly? The conflict happens in Grow.c:Grow_reshap().
> 
> Thanks.
> 
> Coly Li
> 

Hi Coly,
I checked the conflict myself, and the changes on the branch also look
fine for me.

Thanks,
Mateusz

  reply	other threads:[~2022-06-29 13:12 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 [this message]
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
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=43497f54-7b9f-7ad3-b965-b9f83a3fbed3@linux.intel.com \
    --to=mateusz.kusiak@linux.intel.com \
    --cc=colyli@suse.de \
    --cc=jes@trained-monkey.org \
    --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.