netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Ahern <dsahern@gmail.com>
To: Hoang Le <hoang.h.le@dektech.com.au>,
	netdev@vger.kernel.org, tipc-discussion@lists.sourceforge.net
Subject: Re: [iproute2-next v3 1/2] tipc: JSON support for showing nametable
Date: Wed, 13 Jun 2018 21:47:08 -0600	[thread overview]
Message-ID: <84bb9f7f-0785-78a4-9f4d-e88cf04e5d21@gmail.com> (raw)
In-Reply-To: <1528770749-10415-1-git-send-email-hoang.h.le@dektech.com.au>

On 6/11/18 8:32 PM, Hoang Le wrote:
> Add json output support for nametable show
> 
> Example output:
> $tipc -j -p nametable show
> 
> [ {
>         "type": 0,
>         "lower": 16781313,
>         "upper": 16781313,
>         "scope": "zone",
>         "port": 0,
>         "node": ""
>     },{
>         "type": 0,
>         "lower": 16781416,
>         "upper": 16781416,
>         "scope": "cluster",
>         "port": 0,
>         "node": ""
>     } ]
> 
> v2:
>     Replace variable 'json_flag' by 'json' declared in include/utils.h
>     Add new parameter '-pretty' to support pretty output
> 
> v3:
>     Update manual page
> 
> Acked-by: Jon Maloy <jon.maloy@ericsson.com>
> Signed-off-by: Hoang Le <hoang.h.le@dektech.com.au>
> ---
>  man/man8/tipc-nametable.8 | 10 ++++++++++
>  man/man8/tipc.8           |  9 +++++++++
>  tipc/nametable.c          | 31 ++++++++++++++++++++++---------
>  tipc/tipc.c               | 20 +++++++++++++++++++-
>  4 files changed, 60 insertions(+), 10 deletions(-)
> 

applied to iproute2-next. Thanks

      parent reply	other threads:[~2018-06-14  3:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-12  2:32 [iproute2-next v3 1/2] tipc: JSON support for showing nametable Hoang Le
2018-06-12  2:32 ` [iproute2-next v3 2/2] tipc: JSON support for tipc link printouts Hoang Le
2018-06-14  3:47   ` David Ahern
2018-06-14  3:47 ` David Ahern [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=84bb9f7f-0785-78a4-9f4d-e88cf04e5d21@gmail.com \
    --to=dsahern@gmail.com \
    --cc=hoang.h.le@dektech.com.au \
    --cc=netdev@vger.kernel.org \
    --cc=tipc-discussion@lists.sourceforge.net \
    /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).