From: Rusty Russell <rusty@rustcorp.com.au>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, xemul@openvz.org, ebiederm@xmission.com
Subject: Re: [PATCH] Rename "virtual ethernet device" to "virtual ethernet pair device".
Date: Wed, 7 Nov 2007 15:04:48 +1100 [thread overview]
Message-ID: <200711071504.49112.rusty@rustcorp.com.au> (raw)
In-Reply-To: <20071106.191906.127144742.davem@davemloft.net>
On Wednesday 07 November 2007 14:19:06 David Miller wrote:
> If anything, the veth naming makes more sense than the IBM device
> cases.
>
> And that's why I decreed that last time this came up that the naming
> for veth was just fine.
OK, about the help text. IMHO noone should be using "virtual
ethernet" unqualified, since there are multiple things that now refers to.
Here's a respin with just the help text changes:
==
Clarify "virtual ethernet device" to "virtual ethernet pair device".
It'd also be nice to mention "containers" somewhere in the help text
(I'm assuming that's what it's for?).
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
diff --git a/drivers/net/Kconfig b/drivers/net/Kconfig
index 5f800a6..cb581eb 100644
--- a/drivers/net/Kconfig
+++ b/drivers/net/Kconfig
@@ -136,10 +136,11 @@ config TUN
If you don't know what to use this for, you don't need it.
config VETH
- tristate "Virtual ethernet device"
+ tristate "Virtual ethernet pair device"
---help---
- The device is an ethernet tunnel. Devices are created in pairs. When
- one end receives the packet it appears on its pair and vice versa.
+ This device is a local ethernet tunnel. Devices are created in pairs.
+ When one end receives the packet it appears on its pair and vice
+ versa.
config NET_SB1000
tristate "General Instruments Surfboard 1000"
next prev parent reply other threads:[~2007-11-07 4:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-07 3:09 [PATCH] Rename "virtual ethernet device" to "virtual ethernet pair device" Rusty Russell
2007-11-07 3:19 ` David Miller
2007-11-07 4:04 ` Rusty Russell [this message]
2007-11-07 4:36 ` David 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=200711071504.49112.rusty@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=davem@davemloft.net \
--cc=ebiederm@xmission.com \
--cc=netdev@vger.kernel.org \
--cc=xemul@openvz.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.