[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87d2ddh1zd.fsf@nemi.mork.no>
Date: Thu, 10 Jul 2014 13:44:54 +0200
From: Bjørn Mork <bjorn@...k.no>
To: Tom Gundersen <teg@...m.no>
Cc: netdev <netdev@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>,
David Miller <davem@...emloft.net>,
David Herrmann <dh.herrmann@...il.com>,
Kay Sievers <kay@...y.org>,
dingtianhong <dingtianhong@...wei.com>,
Tan Xiaojun <tanxiaojun@...wei.com>,
WANG Cong <xiyou.wangcong@...il.com>
Subject: Re: [PATCH v7 10/33] net: dummy - set name assign type
Tom Gundersen <teg@...m.no> writes:
> The result of
>
> modprobe dummy numdummies=2
>
> is to create dummy0 and dummy1, always with the same names.
>
> The result of
>
> ip link add type dummy
>
> is to create dummyX, where X depends on what came before.
Which is no different. That's exacly what happens when
"modprobe dummy numdummies=2" creates the two first interfaces.
ip link add link wwan0 name dummy0 type vlan id 2
modprobe dummy numdummies=2
ends up with dummy1 and dummy2 created by the dummy driver.
You are trying to make up differences that just aren't there.
Bjørn
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists