From: David Miller <davem@davemloft.net>
To: maheshb@google.com
Cc: netdev@vger.kernel.org, edumazet@google.com
Subject: Re: [PATCH net-next 4/4] macvlan: play well with ipvlan device
Date: Tue, 09 Dec 2014 16:10:55 -0500 (EST) [thread overview]
Message-ID: <20141209.161055.1393386731139458138.davem@davemloft.net> (raw)
In-Reply-To: <1417910026-13371-1-git-send-email-maheshb@google.com>
From: Mahesh Bandewar <maheshb@google.com>
Date: Sat, 6 Dec 2014 15:53:46 -0800
> If device is already used as an ipvlan port then refuse to
> use it as a macvlan port at early stage of port creation.
>
> thost1:~# ip link add link eth0 ipvl0 type ipvlan
> thost1:~# echo $?
> 0
> thost1:~# ip link add link eth0 mvl0 type macvlan
> RTNETLINK answers: Device or resource busy
> thost1:~# echo $?
> 2
> thost1:~#
>
> Signed-off-by: Mahesh Bandewar <maheshb@google.com>
Applied.
prev parent reply other threads:[~2014-12-09 21:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-06 23:53 [PATCH net-next 4/4] macvlan: play well with ipvlan device Mahesh Bandewar
2014-12-09 21:10 ` David Miller [this message]
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=20141209.161055.1393386731139458138.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=maheshb@google.com \
--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 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).