From: "David S. Miller" <davem@redhat.com>
To: hadi@cyberus.ca
Cc: ak@muc.de, netdev@oss.sgi.com, jgarzik@pobox.com
Subject: Re: [PATCH] Allow multiple dummy devices again
Date: Thu, 27 Nov 2003 17:40:12 -0800 [thread overview]
Message-ID: <20031127174012.0bab844e.davem@redhat.com> (raw)
In-Reply-To: <1069983202.1041.5.camel@jzny.localdomain>
On 27 Nov 2003 20:33:22 -0500
jamal <hadi@cyberus.ca> wrote:
> On Thu, 2003-11-27 at 20:13, David S. Miller wrote:
>
> > Even though we generally frown upon module options for networking
> > devices, I think it's wholly appropriate for this case.
>
> Why not make it also a boot option?
They're one in the same these days.
If the driver is built as a module, you pass the option in with
at modload time, else you pass it in on the kernel command line.
next prev parent reply other threads:[~2003-11-28 1:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-28 0:44 [PATCH] Allow multiple dummy devices again Andi Kleen
2003-11-28 1:13 ` David S. Miller
2003-11-28 1:33 ` jamal
2003-11-28 1:40 ` David S. Miller [this message]
2003-11-28 7:04 ` Christoph Hellwig
2003-11-28 8:30 ` David S. Miller
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=20031127174012.0bab844e.davem@redhat.com \
--to=davem@redhat.com \
--cc=ak@muc.de \
--cc=hadi@cyberus.ca \
--cc=jgarzik@pobox.com \
--cc=netdev@oss.sgi.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;
as well as URLs for NNTP newsgroup(s).