netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: dlezcano@fr.ibm.com
Cc: xemul@openvz.org, containers@lists.osdl.org,
	netdev@vger.kernel.org, kaber@trash.net, dev@openvz.org
Subject: Re: [Devel] Re: [PATCH] Virtual ethernet tunnel
Date: Wed, 06 Jun 2007 13:49:59 -0700 (PDT)	[thread overview]
Message-ID: <20070606.134959.93210257.davem@davemloft.net> (raw)
In-Reply-To: <46671B33.60907@fr.ibm.com>

From: Daniel Lezcano <dlezcano@fr.ibm.com>
Date: Wed, 06 Jun 2007 22:38:11 +0200

> Perhaps, a name like "epipe" or "npipe", which reflects what does the 
> device, is more appropriate ?

'npipe' (Network PIPE) or 'epipe' (Ethernet PIPE) are fine with me.

  reply	other threads:[~2007-06-06 20:49 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-06 15:11 [PATCH] Virtual ethernet tunnel Pavel Emelianov
2007-06-06 15:17 ` [PATCH] Module for ip utility to support veth device Pavel Emelianov
2007-06-06 15:18   ` Patrick McHardy
2007-06-06 15:28 ` [PATCH] Virtual ethernet tunnel Patrick McHardy
2007-06-07  8:09   ` Pavel Emelianov
2007-06-07  9:29     ` Daniel Lezcano
2007-06-07  9:51       ` Pavel Emelianov
2007-06-07 14:05         ` Daniel Lezcano
2007-06-07 14:23           ` Kirill Korotaev
2007-06-07 14:42             ` Daniel Lezcano
2007-06-07 15:33               ` Pavel Emelianov
2007-06-07 15:25           ` Pavel Emelianov
2007-06-07 15:44             ` Daniel Lezcano
2007-06-11 11:39     ` Patrick McHardy
2007-06-13  9:24       ` Pavel Emelianov
2007-06-13 11:12         ` Patrick McHardy
2007-06-13 16:02           ` Pavel Emelianov
2007-06-13 15:37             ` Patrick McHardy
2007-06-06 15:39 ` Patrick McHardy
2007-06-06 16:17 ` Stephen Hemminger
2007-06-06 19:47 ` David Miller
2007-06-06 20:38   ` [Devel] " Daniel Lezcano
2007-06-06 20:49     ` David Miller [this message]
2007-06-07  8:14   ` Kirill Korotaev
2007-06-07  9:07     ` David Miller
2007-06-07  9:30       ` Benjamin Thery

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=20070606.134959.93210257.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=containers@lists.osdl.org \
    --cc=dev@openvz.org \
    --cc=dlezcano@fr.ibm.com \
    --cc=kaber@trash.net \
    --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 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).