All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com>
To: jes@trained-monkey.org, Coly Li <colyli@suse.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: [PATCH 0/2] Add map_num_s
Date: Tue, 22 Mar 2022 16:28:54 +0100	[thread overview]
Message-ID: <20220322162854.00005881@linux.intel.com> (raw)
In-Reply-To: <20220120121833.16055-1-mariusz.tkaczyk@linux.intel.com>

Hi Coly,
Could you review?

Thanks,
Mariusz

On Thu, 20 Jan 2022 13:18:31 +0100
Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com> wrote:
> Hi Jes,
> In this patchset not null version of map_num() was added.
> Additionally, I propagaded default_layout() for Build mode.
> 
> I tested changes and I didn't find any regression.
> 
> Mariusz Tkaczyk (2):
>   Create, Build: use default_layout()
>   mdadm: add map_num_s()
> 
>  Assemble.c    |  6 ++---
>  Build.c       | 23 +-----------------
>  Create.c      | 67
> +++++++++++++++++++++++++++++++-------------------- Detail.c      |
> 4 +-- Grow.c        | 16 ++++++------
>  Query.c       |  4 +--
>  maps.c        | 24 ++++++++++++++++++
>  mdadm.c       | 20 +++++++--------
>  mdadm.h       |  3 ++-
>  super-ddf.c   |  6 ++---
>  super-intel.c |  2 +-
>  super0.c      |  2 +-
>  super1.c      |  2 +-
>  sysfs.c       |  9 ++++---
>  14 files changed, 103 insertions(+), 85 deletions(-)
> 


      parent reply	other threads:[~2022-03-22 15:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-20 12:18 [PATCH 0/2] Add map_num_s Mariusz Tkaczyk
2022-01-20 12:18 ` [PATCH 1/2] Create, Build: use default_layout() Mariusz Tkaczyk
2022-04-05  1:21   ` Jes Sorensen
2022-01-20 12:18 ` [PATCH 2/2] mdadm: add map_num_s() Mariusz Tkaczyk
2022-04-05  1:32   ` Jes Sorensen
2022-04-05  8:28     ` Mariusz Tkaczyk
2022-03-22 15:28 ` Mariusz Tkaczyk [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=20220322162854.00005881@linux.intel.com \
    --to=mariusz.tkaczyk@linux.intel.com \
    --cc=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 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.