From: "David S. Miller" <davem@redhat.com>
To: Andi Kleen <ak@muc.de>
Cc: netdev@oss.sgi.com, jgarzik@pobox.com
Subject: Re: [PATCH] Allow multiple dummy devices again
Date: Thu, 27 Nov 2003 17:13:13 -0800 [thread overview]
Message-ID: <20031127171313.04f89baa.davem@redhat.com> (raw)
In-Reply-To: <20031128004445.GA2870@averell>
On Fri, 28 Nov 2003 01:44:45 +0100
Andi Kleen <ak@muc.de> wrote:
> In 2.6 the old trick of copying the dummy module to get multiple dummy
> devices doesn't work anymore because the "dummy" device name is embedded
> in the module.
>
> This patch adds a new module option that allows to specify how many
> dummy devices you want.
Jeff, FWIW I'm fine with this.
Even though we generally frown upon module options for networking
devices, I think it's wholly appropriate for this case.
next prev parent reply other threads:[~2003-11-28 1:13 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 [this message]
2003-11-28 1:33 ` jamal
2003-11-28 1:40 ` David S. Miller
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=20031127171313.04f89baa.davem@redhat.com \
--to=davem@redhat.com \
--cc=ak@muc.de \
--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).