From: Roopa Prabhu <roopa@cumulusnetworks.com>
To: Toshiaki Makita <makita.toshiaki@lab.ntt.co.jp>
Cc: stephen@networkplumber.org, netdev@vger.kernel.org,
anuradhak@cumulusnetworks.com, nikolay@cumulusnetworks.com,
julien@cumulusnetworks.com
Subject: Re: [PATCH iproute2 net-next 2/5] bridge: add json support for bridge vlan show
Date: Mon, 30 May 2016 19:17:02 -0700 [thread overview]
Message-ID: <574CF41E.6020605@cumulusnetworks.com> (raw)
In-Reply-To: <92ec8efe-8627-2d3a-736d-4fadce3a8bd8@lab.ntt.co.jp>
On 5/29/16, 5:43 PM, Toshiaki Makita wrote:
> On 2016/05/28 13:37, Roopa Prabhu wrote:
>> From: Roopa Prabhu <roopa@cumulusnetworks.com>
>>
>> $bridge -c vlan show
>> port vlan ids
>> swp1 1 PVID Egress Untagged
>> 10-13
>>
>> swp2 1 PVID Egress Untagged
>> 10-13
>>
>> br0 1 PVID Egress Untagged
>>
>> $bridge -j vlan show
>> {
>> "swp1": [{
>> "vlan": 1,
>> "flags": "PVID Egress Untagged"
> Shouldn't we split flags?
yes, of-course. v2 coming...
prev parent reply other threads:[~2016-05-31 2:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-28 4:37 [PATCH iproute2 net-next 2/5] bridge: add json support for bridge vlan show Roopa Prabhu
2016-05-30 0:43 ` Toshiaki Makita
2016-05-31 2:17 ` Roopa Prabhu [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=574CF41E.6020605@cumulusnetworks.com \
--to=roopa@cumulusnetworks.com \
--cc=anuradhak@cumulusnetworks.com \
--cc=julien@cumulusnetworks.com \
--cc=makita.toshiaki@lab.ntt.co.jp \
--cc=netdev@vger.kernel.org \
--cc=nikolay@cumulusnetworks.com \
--cc=stephen@networkplumber.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.