linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jes Sorensen <jes.sorensen@gmail.com>
To: Pawel Baldysiak <pawel.baldysiak@intel.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: [PATCH 00/12] Multiple PPL support and PPL bugfixes
Date: Mon, 2 Oct 2017 16:16:06 -0400	[thread overview]
Message-ID: <44c99cf5-6c4c-e9ab-ab9d-0e319e82034d@gmail.com> (raw)
In-Reply-To: <20170928124118.23361-1-pawel.baldysiak@intel.com>

On 09/28/2017 08:41 AM, Pawel Baldysiak wrote:
> This patchset introduces userspace support for multiple PPLs written in a
> circular buffer. It also contains few general bug fixes for PPL, and
> couple of IMSM specific compatibility patches related to new PPL.
> 
> Artur Paszkiewicz (5):
>    Don't abort starting the array if kernel does not support ppl
>    imsm: don't skip resync when an invalid ppl header is found
>    imsm: always do ppl recovery when starting a rebuilding array
>    imsm: use correct map when validating ppl
>    imsm: write initial ppl on a disk added for rebuild
> 
> Pawel Baldysiak (7):
>    super1: Add support for multiple-ppls
>    imsm: Add support for multiple ppls
>    imsm: validate multiple ppls during assemble
>    Zeroout whole ppl space during creation/force assemble
>    imsm: switch to multiple ppls automatically during assemble
>    Grow: fix switching on PPL during recovery
>    imsm: Write empty PPL header if assembling regular clean array.
> 
>   Grow.c        |   3 -
>   managemon.c   |  11 +++-
>   mdadm.h       |   1 +
>   super-intel.c | 181 ++++++++++++++++++++++++++++++++++++++++++++--------------
>   super1.c      |  70 ++++++++++++++---------
>   sysfs.c       |   6 +-
>   util.c        |  49 ++++++++++++++++
>   7 files changed, 241 insertions(+), 80 deletions(-)

Applied!

Thanks,
Jes


      parent reply	other threads:[~2017-10-02 20:16 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-28 12:41 [PATCH 00/12] Multiple PPL support and PPL bugfixes Pawel Baldysiak
2017-09-28 12:41 ` [PATCH 01/12] Don't abort starting the array if kernel does not support ppl Pawel Baldysiak
2017-09-28 12:41 ` [PATCH 02/12] super1: Add support for multiple-ppls Pawel Baldysiak
2017-09-28 12:41 ` [PATCH 03/12] imsm: Add support for multiple ppls Pawel Baldysiak
2017-09-28 12:41 ` [PATCH 04/12] imsm: validate multiple ppls during assemble Pawel Baldysiak
2017-09-28 12:41 ` [PATCH 05/12] Zeroout whole ppl space during creation/force assemble Pawel Baldysiak
2017-09-28 12:41 ` [PATCH 06/12] imsm: switch to multiple ppls automatically during assemble Pawel Baldysiak
2017-09-28 12:41 ` [PATCH 07/12] Grow: fix switching on PPL during recovery Pawel Baldysiak
2017-09-28 12:41 ` [PATCH 08/12] imsm: don't skip resync when an invalid ppl header is found Pawel Baldysiak
2017-09-28 12:41 ` [PATCH 09/12] imsm: Write empty PPL header if assembling regular clean array Pawel Baldysiak
2017-09-28 12:41 ` [PATCH 10/12] imsm: always do ppl recovery when starting a rebuilding array Pawel Baldysiak
2017-09-28 12:41 ` [PATCH 11/12] imsm: use correct map when validating ppl Pawel Baldysiak
2017-09-28 12:41 ` [PATCH 12/12] imsm: write initial ppl on a disk added for rebuild Pawel Baldysiak
2017-10-02 20:16 ` 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=44c99cf5-6c4c-e9ab-ab9d-0e319e82034d@gmail.com \
    --to=jes.sorensen@gmail.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=pawel.baldysiak@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 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).