From: Stephen Hemminger <stephen@networkplumber.org>
To: Roopa Prabhu <roopa@cumulusnetworks.com>
Cc: netdev@vger.kernel.org, anuradhak@cumulusnetworks.com,
nikolay@cumulusnetworks.com, julien@cumulusnetworks.com
Subject: Re: [PATCH iproute2 net-next 0/5] bridge: json support for fdb and vlan show
Date: Wed, 20 Jul 2016 12:07:11 -0700 [thread overview]
Message-ID: <20160720120711.3a00a73e@xeon-e3> (raw)
In-Reply-To: <1464410236-65044-1-git-send-email-roopa@cumulusnetworks.com>
On Fri, 27 May 2016 21:37:11 -0700
Roopa Prabhu <roopa@cumulusnetworks.com> wrote:
> From: Roopa Prabhu <roopa@cumulusnetworks.com>
>
> This patch series adds json support for a few bridge show commands.
> We plan to follow up with json support for additional commands soon.
>
> Anuradha Karuppiah (3):
> json_writer: allow base json data type to be array or object
> bridge: add json support for bridge fdb show
> bridge: add json schema for bridge fdb show
>
> Roopa Prabhu (2):
> bridge: add json support for bridge vlan show
> bridge: update man page
>
> bridge/br_common.h | 1 +
> bridge/bridge.c | 3 +
> bridge/fdb.c | 201 +++++++++++++++++++++++++++++++++---------
> bridge/vlan.c | 93 ++++++++++++++++++-
> include/json_writer.h | 5 +-
> lib/json_writer.c | 39 +++++++-
> man/man8/bridge.8 | 9 +-
> misc/ifstat.c | 6 +-
> misc/lnstat.c | 2 +-
> misc/nstat.c | 4 +-
> schema/bridge_fdb_schema.json | 62 +++++++++++++
> 11 files changed, 365 insertions(+), 60 deletions(-)
> create mode 100644 schema/bridge_fdb_schema.json
>
Applied these for current release
prev parent reply other threads:[~2016-07-20 19:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-28 4:37 [PATCH iproute2 net-next 0/5] bridge: json support for fdb and vlan show Roopa Prabhu
2016-07-20 19:07 ` Stephen Hemminger [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=20160720120711.3a00a73e@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=anuradhak@cumulusnetworks.com \
--cc=julien@cumulusnetworks.com \
--cc=netdev@vger.kernel.org \
--cc=nikolay@cumulusnetworks.com \
--cc=roopa@cumulusnetworks.com \
/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.