public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@wirex.com>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: "Adam J. Richter" <adam@yggdrasil.com>, linux-kernel@vger.kernel.org
Subject: Re: Patch(?): linux-2.4.0-test11-pre4/drivers/sound/yss225.c compilefailure
Date: Tue, 14 Nov 2000 21:43:43 -0800	[thread overview]
Message-ID: <20001114214343.A20546@wirex.com> (raw)
In-Reply-To: <200011150102.RAA00924@adam.yggdrasil.com> <3A121F2B.21DB3265@mandrakesoft.com>
In-Reply-To: <3A121F2B.21DB3265@mandrakesoft.com>; from jgarzik@mandrakesoft.com on Wed, Nov 15, 2000 at 12:29:15AM -0500

On Wed, Nov 15, 2000 at 12:29:15AM -0500, Jeff Garzik wrote:
> 
> This is not just a USB issue.  Please discuss this on linux-kernel, so
> we can have a coherent hotplug strategy for the entire kernel.

I agree.  If I see the topic come up on linux-usb-devel again, I'll push
it over to linux-kernel.

> If we are going to create CONFIG_USB_HOTPLUG, we must -eliminate-
> CONFIG_HOTPLUG, and create CONFIG_PCI_HOTPLUG, and
> CONFIG_ANOTHERBUS_HOTPLUG and so on, for each hotplug bus.

Argh!
I thought the whole point of this was to make there be only one hotplug
strategy, due to the fact that this is a real need.

Please let's not go down this path.  It was all starting to look so
nice...

greg k-h

-- 
greg@(kroah|wirex).com
http://immunix.org/~greg
-
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/

  reply	other threads:[~2000-11-15  6:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-15  1:02 Patch(?): linux-2.4.0-test11-pre4/drivers/sound/yss225.c compilefailure Adam J. Richter
2000-11-15  5:29 ` Jeff Garzik
2000-11-15  5:43   ` Greg KH [this message]
2000-11-15  5:54     ` Jeff Garzik
2000-11-15  6:03       ` College of Cardinals Vote!!! Andre Hedrick
2000-11-15  6:52       ` Patch(?): linux-2.4.0-test11-pre4/drivers/sound/yss225.c compilefailure Greg KH
  -- strict thread matches above, loose matches on Subject: below --
2000-11-15  8:32 Adam J. Richter
2000-11-15  7:58 Adam J. Richter
2000-11-14 22:56 Patch(?): linux-2.4.0-test11-pre4/drivers/sound/yss225.c compile failure Bartlomiej Zolnierkiewicz
2000-11-14 23:01 ` Patch(?): linux-2.4.0-test11-pre4/drivers/sound/yss225.c compilefailure Jeff Garzik
2000-11-14 23:17   ` Bartlomiej Zolnierkiewicz

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=20001114214343.A20546@wirex.com \
    --to=greg@wirex.com \
    --cc=adam@yggdrasil.com \
    --cc=jgarzik@mandrakesoft.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox