From: Paul Gortmaker <p_gortmaker@yahoo.com>
To: Keith Owens <kaos@ocs.com.au>
Cc: David Luyer <david_luyer@pacific.net.au>,
alan@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: PATCH: "Pass module parameters" to built-in drivers
Date: Wed, 24 Jan 2001 08:32:35 -0500 [thread overview]
Message-ID: <3A6ED972.6636E169@yahoo.com> (raw)
In-Reply-To: <27169.980053744@ocs3.ocs-net>
Keith Owens wrote:
> Inconsistent methods for setting the same parameter are bad. I can and
> will do this cleanly in 2.5. Parameters will be always be keyed by the
> module name, even if they are compiled in. Adding an inconsistent
I'm curious as to what boot argument equivalent you envision for e.g.
options ne io=0x280,0x300 irq=10,12 bad=0,1
> method to 2.4 then changing to a correct method in 2.5 is a bad idea,
> wait until we can do it right.
As a related issue, this will allow me (or whoever) to kill off the
ether=x,y,z,ethN boot argument for compiled in ethernet drivers at
the same time. It made sense back in 1.0/1.2 days when distro kernels
were shipped with everything compiled in and ISA cards were the norm.
Now it is hardly used and generally a PITA to support.
Paul.
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
-
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/
next prev parent reply other threads:[~2001-01-24 14:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-21 4:54 PATCH: "Pass module parameters" to built-in drivers David Luyer
2001-01-21 5:09 ` Keith Owens
2001-01-22 15:56 ` Werner Almesberger
2001-01-22 16:30 ` Keith Owens
2001-01-22 18:08 ` Werner Almesberger
2001-01-22 21:55 ` Russell King
2001-01-23 6:37 ` Keith Owens
2001-01-23 9:18 ` Richard Guenther
2001-01-24 13:32 ` Paul Gortmaker [this message]
2001-01-24 20:57 ` Keith Owens
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=3A6ED972.6636E169@yahoo.com \
--to=p_gortmaker@yahoo.com \
--cc=alan@redhat.com \
--cc=david_luyer@pacific.net.au \
--cc=kaos@ocs.com.au \
--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