From: Stephen Hemminger <stephen@networkplumber.org>
To: Jiri Pirko <jiri@resnulli.us>
Cc: Roopa Prabhu <roopa@cumulusnetworks.com>,
netdev@vger.kernel.org, anuradhak@cumulusnetworks.com,
nikolay@cumulusnetworks.com, julien@cumulusnetworks.com
Subject: Re: [PATCH iproute2 net-next v4 0/5] bridge: json support for fdb and vlan show
Date: Wed, 22 Jun 2016 11:10:47 -0700 [thread overview]
Message-ID: <20160622111047.1523b06f@xeon-e3> (raw)
In-Reply-To: <20160622145344.GE2068@nanopsycho.orion>
On Wed, 22 Jun 2016 16:53:44 +0200
Jiri Pirko <jiri@resnulli.us> wrote:
> Wed, Jun 22, 2016 at 03:45:50PM CEST, 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.
>
> I'm just curious, what is you use case for this? Apps can use rtnetlink
> socket directly.
Try using netlink in perl or python, it is quite difficult.
next prev parent reply other threads:[~2016-06-22 18:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-22 13:45 [PATCH iproute2 net-next v4 0/5] bridge: json support for fdb and vlan show Roopa Prabhu
2016-06-22 13:45 ` [PATCH iproute2 net-next v4 1/5] json_writer: Removed automatic json-object type from the constructor Roopa Prabhu
2016-06-22 13:45 ` [PATCH iproute2 net-next v4 2/5] bridge: add json support for bridge vlan show Roopa Prabhu
2016-06-22 13:45 ` [PATCH iproute2 net-next v4 3/5] bridge: add json support for bridge fdb show Roopa Prabhu
2016-06-22 13:45 ` [PATCH iproute2 net-next v4 4/5] bridge: add json schema " Roopa Prabhu
2016-06-22 13:45 ` [PATCH iproute2 net-next v4 5/5] bridge: update man page Roopa Prabhu
2016-06-22 14:53 ` [PATCH iproute2 net-next v4 0/5] bridge: json support for fdb and vlan show Jiri Pirko
2016-06-22 17:41 ` Roopa Prabhu
2016-06-22 18:10 ` Stephen Hemminger [this message]
2016-06-22 18:23 ` Roopa Prabhu
2016-06-22 20:00 ` Jiri Pirko
2016-06-23 11:03 ` Roopa Prabhu
2016-06-25 6:20 ` Rami Rosen
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=20160622111047.1523b06f@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=anuradhak@cumulusnetworks.com \
--cc=jiri@resnulli.us \
--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 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).