From: "John Stoffel" <stoffel@lucent.com>
To: Tomas Szepe <szepe@pinerecords.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Stephen Hemminger <shemminger@osdl.org>,
James Ketrenos <jketreno@linux.intel.com>,
Pavel Machek <pavel@suse.cz>,
Jeff Chua <jeffchua@silk.corp.fedex.com>,
netdev@oss.sgi.com, kernel list <linux-kernel@vger.kernel.org>
Subject: Re: ipw2100 wireless driver
Date: Wed, 11 Aug 2004 14:55:28 -0400 [thread overview]
Message-ID: <16666.27552.585978.551609@gargle.gargle.HOWL> (raw)
In-Reply-To: <20040811170208.GG10100@louise.pinerecords.com>
Tomas> On Aug-11 2004, Wed, 17:51 +0100
Tomas> Christoph Hellwig <hch@infradead.org> wrote:
>> On Wed, Aug 11, 2004 at 06:33:33PM +0200, Tomas Szepe wrote:
>> > There are many people who don't want to mess around with hotplug just
>> > to get a single driver to load.
>>
>> Then use a distribution that gets it right for you. Having gazillions
>> of diffferent firmware loaders just because people are too lazy to set
>> up the canonical one isn't where we want to go.
Tomas> Agreed. But the point is, in the actual case of ipw2100, will
Tomas> the removal of 40 or so lines of code justify killing the
Tomas> functionality for those (lots) that use it? I don't think so.
You can't have your cake and eat it too Tomas! You agree that having
multiple firmware loaders in the kernel is bad, yet you still want to
have your own special one in there? What's so difficult about setting
up hotplug for this purpose anyway?
John
next prev parent reply other threads:[~2004-08-11 18:56 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-14 11:41 Pavel Machek
2004-07-14 11:48 ` Jeff Chua
2004-07-14 11:55 ` Pavel Machek
2004-07-14 14:53 ` Éric Brunet
2004-07-14 15:24 ` Emiliano 'AlberT' Gabrielli
2004-08-09 20:15 ` Tomas Szepe
2004-08-10 5:02 ` Jeff Chua
2004-08-10 6:55 ` Christoph Hellwig
2004-08-10 10:16 ` Pavel Machek
2004-08-10 10:34 ` Christoph Hellwig
2004-08-11 12:17 ` Pavel Machek
2004-08-11 17:54 ` Jeff Garzik
2004-08-11 20:27 ` Pavel Machek
2004-08-11 22:01 ` Jeff Garzik
2004-08-11 10:16 ` James Ketrenos
2004-08-11 10:44 ` Christoph Hellwig
2004-08-11 10:53 ` Wichert Akkerman
2004-08-11 10:59 ` Christoph Hellwig
2004-08-11 16:21 ` James Ketrenos
2004-08-11 16:30 ` Stephen Hemminger
2004-08-11 16:33 ` Tomas Szepe
2004-08-11 16:51 ` Christoph Hellwig
2004-08-11 17:02 ` Tomas Szepe
2004-08-11 17:11 ` Christoph Hellwig
2004-08-11 17:22 ` Tomas Szepe
2004-08-11 17:41 ` Christoph Hellwig
2004-08-11 17:51 ` Tomas Szepe
2004-08-11 22:43 ` David Woodhouse
2004-08-11 22:56 ` Tomas Szepe
2004-08-11 23:06 ` David Woodhouse
2004-08-11 23:11 ` Tomas Szepe
2004-08-11 23:21 ` David Woodhouse
2004-08-11 18:55 ` John Stoffel [this message]
2004-08-11 23:55 ` Jeff Chua
2004-08-12 3:47 ` Luis R. Rodriguez
2004-08-11 17:51 ` Jeff Garzik
2004-07-14 12:30 ` Tomas Szepe
2004-07-14 12:27 ` Pavel Machek
2004-07-14 13:15 ` Vojtech Pavlik
2004-07-14 13:42 ` Pavel Machek
2004-07-14 17:00 ` Victor J. Orlikowski
[not found] <2hQr1-62p-23@gated-at.bofh.it>
[not found] ` <2hRQ5-7bn-9@gated-at.bofh.it>
2004-07-14 14:07 ` Andi Kleen
2004-07-14 14:59 ` Vojtech Pavlik
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=16666.27552.585978.551609@gargle.gargle.HOWL \
--to=stoffel@lucent.com \
--cc=hch@infradead.org \
--cc=jeffchua@silk.corp.fedex.com \
--cc=jketreno@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=pavel@suse.cz \
--cc=shemminger@osdl.org \
--cc=szepe@pinerecords.com \
/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
all inboxes | Powered by JetHome®