All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Emelianov <xemul@openvz.org>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: David Miller <davem@davemloft.net>,
	Patrick McHardy <kaber@trash.net>,
	Linux Netdev List <netdev@vger.kernel.org>,
	Daniel Lezcano <dlezcano@fr.ibm.com>,
	Ben Greear <greearb@candelatech.com>,
	devel@openvz.org, Kirill Korotaev <dev@openvz.org>
Subject: Re: [PATCH] Virtual ethernet device (v2.1)
Date: Wed, 11 Jul 2007 16:24:20 +0400	[thread overview]
Message-ID: <4694CBF4.8090303@openvz.org> (raw)
In-Reply-To: <200707111254.24352.borntraeger@de.ibm.com>

Christian Borntraeger wrote:
> Am Mittwoch, 11. Juli 2007 schrieb Pavel Emelianov:
>>  drivers/net/veth.c   |  452 
>>  include/net/veth.h   |   14 +
> 
> I know, I am late in the game, but wont the name collide somewhat with 
> drivers/net/ibmveth.h, drivers/net/iseries_veth.c, and drivers/net/ibmveth.c?

David asked the same thing after v.1. The answer is :
No it will not. These devices use eth%d strings to generate their names.

> Christian
> 

Thanks,
Pavel

  reply	other threads:[~2007-07-11 12:24 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-11  9:31 [PATCH] Virtual ethernet device (v2.1) Pavel Emelianov
2007-07-11  9:33 ` [PATCH] Module for ip utility to support veth device (v.2.1) Pavel Emelianov
2007-07-11  9:44 ` [PATCH] Virtual ethernet device (v2.1) Evgeniy Polyakov
2007-07-11 10:54 ` Christian Borntraeger
2007-07-11 12:24   ` Pavel Emelianov [this message]
2007-07-11 20:45   ` David Miller
2007-07-11 12:23 ` Patrick McHardy
2007-07-11 12:44   ` Pavel Emelianov
2007-07-11 12:53     ` Patrick McHardy
2007-07-11 13:00       ` Pavel Emelianov
2007-07-11 13:12         ` Patrick McHardy
2007-07-11 13:32           ` Pavel Emelianov
2007-07-11 17:32             ` Patrick McHardy

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=4694CBF4.8090303@openvz.org \
    --to=xemul@openvz.org \
    --cc=borntraeger@de.ibm.com \
    --cc=davem@davemloft.net \
    --cc=dev@openvz.org \
    --cc=devel@openvz.org \
    --cc=dlezcano@fr.ibm.com \
    --cc=greearb@candelatech.com \
    --cc=kaber@trash.net \
    --cc=netdev@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 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.