netdev - Re: [PATCH iproute2-next] tc: pedit: Support JSON dumping

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20200422130245.53026ff7@hermes.lan>
Date:   Wed, 22 Apr 2020 13:02:45 -0700
From:   Stephen Hemminger <stephen@...workplumber.org>
To:     Petr Machata <petrm@...lanox.com>
Cc:     netdev@...r.kernel.org, dsahern@...il.com
Subject: Re: [PATCH iproute2-next] tc: pedit: Support JSON dumping

On Wed, 22 Apr 2020 20:06:15 +0300
Petr Machata <petrm@...lanox.com> wrote:

> +			print_string(PRINT_FP, NULL, ": %s",
> +				     cmd ? "add" : "val");
> +			print_string(PRINT_JSON, "cmd", NULL,
> +				     cmd ? "add" : "set");

Having different outputs for JSON and file here. Is that necessary?
JSON output is new, and could just mirror existing usage.