All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Brassow <jbrassow@redhat.com>
To: linux-raid@vger.kernel.org
Subject: [PATCH 0 of 8] Various MD patches to support device-mapper interaction
Date: Tue, 07 Jun 2011 17:45:33 -0500	[thread overview]
Message-ID: <1307486733.31279.4.camel@f14.redhat.com> (raw)

Neil,

Please consider	the following patches for inclusion:

1) md-no-integrity-register-if-no-gendisk.patch
E-mail received 5/24/2011 of patch application, but it has not yet
landed in 3.0.0-rc2

2) md-no-sync-IO-while-suspended.patch
E-mail received 5/24/2011 of patch application, but it has not yet
landed in 3.0.0-rc2

3) md-possible-typo.patch
You mentioned you might	take this one if I changed the message instead
of the parameter value.  I've s/ blocks/k/ - better?

4) md-move-thread-wakeups-into-resume.patch
No comments on this yet.

5) md-raid1-changes-to-allow-use-by-device-mapper.patch
No comments on this yet.

6) md-add-sync_super-to-mddev_t-struct.patch
This is	the patch I'm proposing	as the substitute to the 'analyze_sbs'
patches I had originally posted.  We add a function pointer that can be
called from device-mapper for the purposes of updating the superblock.
(This way, the superblock and 'super_types' functions can be in
dm-raid.c.)

7) md-add-bitmap-support.patch
Bitmap support for device-mapper created arrays.

8) md-raid5-do-not-set-fullsync.patch
A somewhat hackish way around the problem of RAID5 setting fullsync on a
device that merely suffered a transient failure.

Thanks,
 brassow



             reply	other threads:[~2011-06-07 22:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-07 22:45 Jonathan Brassow [this message]
2011-06-08  5:21 ` [PATCH 0 of 8] Various MD patches to support device-mapper interaction NeilBrown

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=1307486733.31279.4.camel@f14.redhat.com \
    --to=jbrassow@redhat.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 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.