netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tomas Szepe <szepe@pinerecords.com>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: James Ketrenos <jketreno@linux.intel.com>,
	Christoph Hellwig <hch@infradead.org>,
	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 18:33:33 +0200	[thread overview]
Message-ID: <20040811163333.GE10100@louise.pinerecords.com> (raw)
In-Reply-To: <20040811093043.522cc5a0@dell_ss3.pdx.osdl.net>

On Aug-11 2004, Wed, 09:30 -0700
Stephen Hemminger <shemminger@osdl.org> wrote:

> > The driver supports (and defaults to) using firmware_class for loading the 
> > firmware.  The driver also supports a legacy loading approach for folks that 
> > have problems with using hotplug to load the firmware (which represents a fair 
> > number of users).
> When and if you submit it into mainline, please remove the legacy loading
> approach. Let's get to the cause of the problem and fix it, not bandaid
> around it.

Or better yet, let's not!

There are many people who don't want to mess around with hotplug just
to get a single driver to load.

-- 
Tomas Szepe <szepe@pinerecords.com>

  reply	other threads:[~2004-08-11 16:33 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-14 11:41 ipw2100 wireless driver Pavel Machek
2004-07-14 11:48 ` Jeff Chua
2004-07-14 11:55   ` Pavel Machek
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 [this message]
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 18:55                           ` John Stoffel
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

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=20040811163333.GE10100@louise.pinerecords.com \
    --to=szepe@pinerecords.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 \
    /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).