linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Miles Lane <miles@megapath.net>
To: linux-hotplug@vger.kernel.org
Subject: Frwd. from LKML -- Re: RAID1/RAID5 hot-add/hot-remove patch?
Date: Wed, 31 Jan 2001 15:54:53 +0000	[thread overview]
Message-ID: <marc-linux-hotplug-98095642324950@msgid-missing> (raw)

Hi Mingo, 

Have you joined the linux-hotplug-devel list?
It sounds like it might be helpful for you to be involved
in defining how a chunk of Hotplug support evolves.

Have you looked into the /sbin/hotplug approach?

	Miles

Quim K Holland wrote:
> 
> Thanks for your reply.
> 
> On the same topic; I am also wondering if there is a reason
> why your RAID1/RAID5 hot-add/hot-remove patch (originally against
> 2.4.0-ac9, Message-ID: <Pine.LNX.4.30.0101151248200.1398-200000@e2>)
> does not go into Linus tree.
> 
> I saw Neil Brown commenting on the patch in linux-raid list in
> <http://marc.theaimsgroup.com/?l=linux-raid&m˜028199906903&w=2>
> (he was suggesting to revert it for somebody who had raid related
> crashes), but do not know what happened after that discussion.
> Alan Cox still seems to have the hot-add/hot-remove patch in his
> tree as of 2.4.0-ac12.
> 
> ------------------------------------------------------------
> --= Sent via Deja.com =--
> http://www.deja.com/
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> Please read the FAQ at http://www.tux.org/lkml/

_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
http://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

                 reply	other threads:[~2001-01-31 15:54 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=marc-linux-hotplug-98095642324950@msgid-missing \
    --to=miles@megapath.net \
    --cc=linux-hotplug@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).