From: Stephen Hemminger <stephen@networkplumber.org>
To: Roi Dayan <roid@mellanox.com>
Cc: netdev@vger.kernel.org, David Ahern <dsahern@gmail.com>,
Jiri Pirko <jiri@mellanox.com>,
Eli Britstein <elibr@mellanox.com>
Subject: Re: [PATCH iproute2 v2 0/5] fix json output for some keys
Date: Tue, 19 Nov 2019 11:40:32 -0800 [thread overview]
Message-ID: <20191119114032.15d0c4db@hermes.lan> (raw)
In-Reply-To: <20191114124441.2261-1-roid@mellanox.com>
On Thu, 14 Nov 2019 14:44:36 +0200
Roi Dayan <roid@mellanox.com> wrote:
> Hi,
>
> This series is fixing output for tos, ttl, ct_zone, ct_mark
> in json format.
>
> Thanks,
> Roi
>
> Eli Britstein (5):
> tc_util: introduce a function to print JSON/non-JSON masked numbers
> tc_util: add an option to print masked numbers with/without a newline
> tc: flower: fix newline prints for ct-mark and ct-zone
> tc_util: fix JSON prints for ct-mark and ct-zone
> tc: flower: fix output for ip tos and ttl
>
> tc/f_flower.c | 19 +++-----------
> tc/m_ct.c | 4 +--
> tc/tc_util.c | 79 +++++++++++++++++++++++++++++++++++++++--------------------
> tc/tc_util.h | 6 +++--
> 4 files changed, 62 insertions(+), 46 deletions(-)
>
Applied, thanks
prev parent reply other threads:[~2019-11-19 19:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-14 12:44 [PATCH iproute2 v2 0/5] fix json output for some keys Roi Dayan
2019-11-14 12:44 ` [PATCH iproute2 v2 1/5] tc_util: introduce a function to print JSON/non-JSON masked numbers Roi Dayan
2019-11-14 23:13 ` Stephen Hemminger
2019-11-17 9:10 ` Roi Dayan
2019-11-14 12:44 ` [PATCH iproute2 v2 2/5] tc_util: add an option to print masked numbers with/without a newline Roi Dayan
2019-11-14 12:44 ` [PATCH iproute2 v2 3/5] tc: flower: fix newline prints for ct-mark and ct-zone Roi Dayan
2019-11-14 12:44 ` [PATCH iproute2 v2 4/5] tc_util: fix JSON " Roi Dayan
2019-11-14 12:44 ` [PATCH iproute2 v2 5/5] tc: flower: fix output for ip tos and ttl Roi Dayan
2019-11-19 19:40 ` Stephen Hemminger [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=20191119114032.15d0c4db@hermes.lan \
--to=stephen@networkplumber.org \
--cc=dsahern@gmail.com \
--cc=elibr@mellanox.com \
--cc=jiri@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=roid@mellanox.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).