All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: linux-kernel@vger.kernel.org
Cc: Greg KH <greg@kroah.com>
Subject: [ANNOUNCE] HotPlug CPU patch against 2.4.5
Date: Tue, 03 Jul 2001 18:30:19 +1000	[thread overview]
Message-ID: <m15HLZc-000CD6C@localhost> (raw)

Hi all,

	http://sourceforge.net/projects/lhcs/

	Version 0.5 (should actually compile) of the HotPlug CPU Patch
is out.  This adds /sbin/hotplug support (thanks Greg), which is
almost useful.

	Of course, /sbin/hotplug falls far short of allowing you to
stop CPUs from going down or coming up, or do something *before* CPUs
go down or up, and it uses env vars to pass what it's doing, but we've
had worse infrastructure in the kernel *cough*sysctl*cough*.  </rant>

Cheers!
Rusty.
--
Premature optmztion is rt of all evl. --DK

             reply	other threads:[~2001-07-03 10:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-03  8:30 Rusty Russell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-06-16 13:29 [ANNOUNCE] HotPlug CPU patch against 2.4.5 Rusty Russell
2001-06-16 13:59 ` Christoph Hellwig
2001-06-17  5:32   ` Rusty Russell
2001-06-17  5:40     ` Alexander Viro
2001-06-26 17:07 ` Greg KH

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=m15HLZc-000CD6C@localhost \
    --to=rusty@rustcorp.com.au \
    --cc=greg@kroah.com \
    --cc=linux-kernel@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.