netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Ahern <dsahern@kernel.org>
To: Andrea Claudi <aclaudi@redhat.com>, netdev@vger.kernel.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: Re: [PATCH iproute2-next 0/3] misc: convert to high-level json_print API
Date: Sun, 26 Oct 2025 17:24:48 -0600	[thread overview]
Message-ID: <b7443cef-ca2a-4833-bb76-e4f527a98aad@kernel.org> (raw)
In-Reply-To: <cover.1761078778.git.aclaudi@redhat.com>

On 10/21/25 2:39 PM, Andrea Claudi wrote:
> This patch series converts three utilities in the misc/ directory
> (ifstat, nstat, and lnstat) from using the low-level json_writer API to
> the high-level json_print API, ensuring they use the same json printing
> logic of all the other iproute2 tools.
> 
> The JSON output before and after these changes remains the same.
> 
> Andrea Claudi (3):
>   ifstat: convert to high-level json_print API
>   nstat: convert to high-level json_print API
>   lnstat: convert to high-level json_print API
> 
>  misc/ifstat.c | 85 ++++++++++++++++++++++-----------------------------
>  misc/lnstat.c | 17 +++++------
>  misc/nstat.c  | 48 +++++++++++++----------------
>  3 files changed, 65 insertions(+), 85 deletions(-)
> 

applied to iproute2-next; thanks for working on cleanups.

      parent reply	other threads:[~2025-10-26 23:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-21 20:39 [PATCH iproute2-next 0/3] misc: convert to high-level json_print API Andrea Claudi
2025-10-21 20:39 ` [PATCH iproute2-next 1/3] ifstat: " Andrea Claudi
2025-10-21 20:39 ` [PATCH iproute2-next 2/3] nstat: " Andrea Claudi
2025-10-21 20:39 ` [PATCH iproute2-next 3/3] lnstat: " Andrea Claudi
2025-10-26 23:24 ` 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=b7443cef-ca2a-4833-bb76-e4f527a98aad@kernel.org \
    --to=dsahern@kernel.org \
    --cc=aclaudi@redhat.com \
    --cc=netdev@vger.kernel.org \
    --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 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).