linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: NeilBrown <neilb@cse.unsw.edu.au>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-raid@vger.kernel.org
Subject: [PATCH md 000 of 2] Introduction
Date: Fri, 26 Aug 2005 17:25:19 +1000	[thread overview]
Message-ID: <20050826172148.16280.patches@notabene> (raw)

Following are two very trivial patches against 2.6.13-rc6.
If 2.6.13 is still open for such trivial fixes, it would be good for
them to go in, but if not, I won't loose any sleep over it.

The first arranges that the first open of /dev/mdX will auto-load the
md modules (I don't know when that functionality disappeared).
The second fixes a possibly problem where-by if you stop an array and
create a new one on the same md device, it might not start any resync
that might be needed.

Thanks,
NeilBrown


 [PATCH md 001 of 2] Create a MODULE_ALIAS for md corresponding to it's block major number.
 [PATCH md 002 of 2] Clear the 'recovery' flags when starting an md array.

             reply	other threads:[~2005-08-26  7:25 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-26  7:25 NeilBrown [this message]
2005-08-26  7:25 ` [PATCH md 001 of 2] Create a MODULE_ALIAS for md corresponding to it's block major number NeilBrown
2005-08-26  7:25 ` [PATCH md 002 of 2] Clear the 'recovery' flags when starting an md array NeilBrown
  -- strict thread matches above, loose matches on Subject: below --
2005-12-05  3:17 [PATCH md 000 of 2] Introduction NeilBrown
2005-11-15  1:56 NeilBrown
2005-11-15 16:55 ` Mr. James W. Laferriere
2005-11-17  5:12   ` Neil Brown
2005-11-17 16:19     ` Mr. James W. Laferriere
2005-10-31  5:58 NeilBrown
2005-10-31  7:34 ` Andrew Morton
2005-10-31  6:44   ` Neil Brown
2005-10-31  7:56     ` Andrew Morton
2005-10-31 14:45     ` Mr. James W. Laferriere
2005-10-31 21:54       ` Neil Brown
2005-05-13  4:51 NeilBrown
2005-04-08  1:41 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=20050826172148.16280.patches@notabene \
    --to=neilb@cse.unsw.edu.au \
    --cc=akpm@osdl.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 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).