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 22:52:01 -0800	[thread overview]
Message-ID: <20001114225201.B20546@wirex.com> (raw)
In-Reply-To: <200011150102.RAA00924@adam.yggdrasil.com> <3A121F2B.21DB3265@mandrakesoft.com> <20001114214343.A20546@wirex.com> <3A12251B.7F600351@mandrakesoft.com>
In-Reply-To: <3A12251B.7F600351@mandrakesoft.com>; from jgarzik@mandrakesoft.com on Wed, Nov 15, 2000 at 12:54:35AM -0500

On Wed, Nov 15, 2000 at 12:54:35AM -0500, Jeff Garzik wrote:
> 
> I -want- there to be only one hotplug strategy, but Adam seemed to be
> talking about the opposite, with his CONFIG_USB_HOTPLUG suggestion.

Here's Adam's proposal for CONFIG_USB_HOTPLUG:
	http://www.geocrawler.com/lists/3/SourceForge/2571/250/4599696/

>From what I remember (and from looking at this message), all he seems to
want is to redefine the __init and __initdata macros depending on a
config item.  There's no other grander scheme of things, right Adam?

Although such a small memory savings for turning a bus whose main goal
in life is to enable hot plugged devices into a fixed connection doesn't
seem worth it.  

We are talking embedded USB hosts here, not devices.  USB devices
running Linux is a whole 'nother thing, which I'm just now starting to
look into...

Comments Adam?

thanks,

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/

  parent reply	other threads:[~2000-11-15  7:22 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
2000-11-15  5:54     ` Jeff Garzik
2000-11-15  6:03       ` College of Cardinals Vote!!! Andre Hedrick
2000-11-15  6:52       ` Greg KH [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-11-15  8:32 Patch(?): linux-2.4.0-test11-pre4/drivers/sound/yss225.c compilefailure 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=20001114225201.B20546@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