From: Stephen Hemminger <stephen@networkplumber.org>
To: Wen Liang <liangwen12year@gmail.com>
Cc: netdev@vger.kernel.org, dsahern@gmail.com, aclaudi@redhat.com
Subject: Re: [PATCH iproute2 v2 1/2] tc: u32: add support for json output
Date: Thu, 28 Oct 2021 14:13:14 -0700 [thread overview]
Message-ID: <20211028141314.652a6142@hermes.local> (raw)
In-Reply-To: <b3310b7f38cdcd5a1b2fa14671af16821e895303.1635434027.git.liangwen12year@gmail.com>
On Thu, 28 Oct 2021 11:25:01 -0400
Wen Liang <liangwen12year@gmail.com> wrote:
> + print_0xhex(PRINT_ANY, "fwmark_value", "\n mark 0x%04x ", mark->val);
> + print_0xhex(PRINT_ANY, "fwmark_mask", "0x%04x ", mark->mask);
Use print_nl() which handles oneline mode rather than explicit newline print
next prev parent reply other threads:[~2021-10-28 21:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-28 15:25 [PATCH iproute2 v2 0/2] add json support on tc u32 Wen Liang
2021-10-28 15:25 ` [PATCH iproute2 v2 1/2] tc: u32: add support for json output Wen Liang
2021-10-28 21:12 ` Stephen Hemminger
2021-10-28 21:13 ` Stephen Hemminger [this message]
2021-10-28 15:25 ` [PATCH iproute2 v2 2/2] tc: u32: add json support in `print_raw`, `print_ipv4`, `print_ipv6` Wen Liang
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=20211028141314.652a6142@hermes.local \
--to=stephen@networkplumber.org \
--cc=aclaudi@redhat.com \
--cc=dsahern@gmail.com \
--cc=liangwen12year@gmail.com \
--cc=netdev@vger.kernel.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).