From: Stephen Hemminger <stephen@networkplumber.org>
To: Davide Caratti <dcaratti@redhat.com>
Cc: David Ahern <dsahern@gmail.com>,
Jamal Hadi Salim <jhs@mojatatu.com>,
Andrea Claudi <aclaudi@redhat.com>,
netdev@vger.kernel.org
Subject: Re: [PATCH iproute2-next] tc: full JSON support for 'bpf' filter
Date: Tue, 28 Apr 2020 08:39:19 -0700 [thread overview]
Message-ID: <20200428083919.355609a0@hermes.lan> (raw)
In-Reply-To: <57923a5a17573e7939a78a55ba5b6dd28ad1862f.1588064112.git.dcaratti@redhat.com>
On Tue, 28 Apr 2020 11:00:07 +0200
Davide Caratti <dcaratti@redhat.com> wrote:
> + print_hex(PRINT_ANY, "handle", "handle 0x%x ", handle);
Do you want print_0xhex instead?
prev parent reply other threads:[~2020-04-28 15:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-28 9:00 [PATCH iproute2-next] tc: full JSON support for 'bpf' filter Davide Caratti
2020-04-28 9:09 ` Andrea Claudi
2020-04-28 15:39 ` 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=20200428083919.355609a0@hermes.lan \
--to=stephen@networkplumber.org \
--cc=aclaudi@redhat.com \
--cc=dcaratti@redhat.com \
--cc=dsahern@gmail.com \
--cc=jhs@mojatatu.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).