From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <netdev-owner@vger.kernel.org>
Received: from mail-pf0-f177.google.com ([209.85.192.177]:44089 "EHLO
        mail-pf0-f177.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1752784AbeCFXvX (ORCPT
        <rfc822;netdev@vger.kernel.org>); Tue, 6 Mar 2018 18:51:23 -0500
Received: by mail-pf0-f177.google.com with SMTP id 17so188542pfw.11
        for <netdev@vger.kernel.org>; Tue, 06 Mar 2018 15:51:23 -0800 (PST)
Subject: Re: [PATCH iproute2-next v2 00/12] ip more JSON
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: netdev@vger.kernel.org, Stephen Hemminger <sthemmin@microsoft.com>
References: <20180306210720.19802-1-stephen@networkplumber.org>
From: David Ahern <dsahern@gmail.com>
Message-ID: <b31fb954-a9ee-e039-9f44-9fb8daec54dd@gmail.com>
Date: Tue, 6 Mar 2018 16:51:20 -0700
MIME-Version: 1.0
In-Reply-To: <20180306210720.19802-1-stephen@networkplumber.org>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Sender: netdev-owner@vger.kernel.org
List-ID: <netdev.vger.kernel.org>

On 3/6/18 2:07 PM, Stephen Hemminger wrote:
> From: Stephen Hemminger <sthemmin@microsoft.com>
> 
> The ip command implementation of JSON was very spotty. Only address
> and link were originally implemented. After doing route for next,
> went ahead and implemented it for a bunch of the other sub commands.
> 
> Hopefully will reach full coverage soon.
> 
> Stephen Hemminger (12):
>   ipneigh: add color and json support
>   ipaddrlabel: add json support
>   iprule: add json support
>   ipntable: add json support
>   ipnetconf: add JSON support
>   tcp_metrics; make tables const
>   tcp_metrics: add json support
>   ipsr: add json support
>   token: support JSON
>   tuntap: support JSON output
>   fou: break long lines
>   fou: support JSON output
> 

applied to iproute2-next.

glad to see the json support. Thanks for working on it.