Linux RAID subsystem development
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.com>
To: Jes Sorensen <jes.sorensen@gmail.com>
Cc: Linux-RAID <linux-raid@vger.kernel.org>
Subject: [mdadm PATCH 0/5] Assorted mdadm patch
Date: Mon, 27 Mar 2017 14:36:55 +1100	[thread overview]
Message-ID: <149058575542.15679.9804611071393072863.stgit@noble> (raw)

I found these while tidying up....
I post a couple already, but then realised that I
have quite a few, so here they are all together.
Sorry for the duplication.

NeilBrown


---

Hannes Reinecke (1):
      udev-md-raid-assembly.rules: Skip non-ready devices

NeilBrown (4):
      Retry HOT_REMOVE_DISK a few times.
      Introduce sys_hot_remove_disk()
      Add 'force' flag to *hot_remove_disk().
      Detail: handle non-existent arrays better.


 Detail.c                    |    8 ++++++++
 Grow.c                      |    9 +--------
 Manage.c                    |   14 +++++---------
 mdadm.h                     |    2 ++
 udev-md-raid-assembly.rules |    3 +++
 util.c                      |   30 ++++++++++++++++++++++++++++++
 6 files changed, 49 insertions(+), 17 deletions(-)

--
Signature


             reply	other threads:[~2017-03-27  3:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-27  3:36 NeilBrown [this message]
2017-03-27  3:36 ` [mdadm PATCH 2/5] Retry HOT_REMOVE_DISK a few times NeilBrown
2017-03-27  7:51   ` 王金浦
2017-03-27  3:36 ` [mdadm PATCH 1/5] udev-md-raid-assembly.rules: Skip non-ready devices NeilBrown
2017-03-27  3:36 ` [mdadm PATCH 4/5] Add 'force' flag to *hot_remove_disk() NeilBrown
2017-03-27  8:05   ` 王金浦
2017-03-28 18:33   ` jes.sorensen
2017-03-27  3:36 ` [mdadm PATCH 5/5] Detail: handle non-existent arrays better NeilBrown
2017-03-28 18:34   ` jes.sorensen
2017-03-27  3:36 ` [mdadm PATCH 3/5] Introduce sys_hot_remove_disk() NeilBrown
2017-03-28 18:33   ` jes.sorensen

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=149058575542.15679.9804611071393072863.stgit@noble \
    --to=neilb@suse.com \
    --cc=jes.sorensen@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox