From: David Ahern <dsahern@gmail•com>
To: Davide Caratti <dcaratti@redhat•com>,
Stephen Hemminger <stephen@networkplumber•org>
Cc: Andrea Claudi <aclaudi@redhat•com>, netdev@vger•kernel.org
Subject: Re: [PATCH iproute2-next] use print_{,h}hu instead of print_uint when format specifier is %{,h}hu
Date: Sun, 10 Feb 2019 20:01:33 -0700 [thread overview]
Message-ID: <87560af9-970c-d36d-e1de-e13c593e4b33@gmail.com> (raw)
In-Reply-To: <318e07e5b1d43e31f9664ff0b3628d4f2994aea9.1549536471.git.dcaratti@redhat.com>
On 2/7/19 3:51 AM, Davide Caratti wrote:
> in this way, a useless cast to unsigned int is avoided in bpf_print_ops()
> and print_tunnel().
>
> Tested with:
> # ./tdc.py -c bpf
>
> Suggested-by: Stephen Hemminger <stephen@networkplumber•org>
> Cc: Andrea Claudi <aclaudi@redhat•com>
> Signed-off-by: Davide Caratti <dcaratti@redhat•com>
> ---
> ip/ipl2tp.c | 4 ++--
> lib/bpf.c | 6 +++---
> 2 files changed, 5 insertions(+), 5 deletions(-)
>
applied to iproute2-next. Thanks
prev parent reply other threads:[~2019-02-11 3:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-07 10:51 [PATCH iproute2-next] use print_{,h}hu instead of print_uint when format specifier is %{,h}hu Davide Caratti
2019-02-11 3:01 ` 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=87560af9-970c-d36d-e1de-e13c593e4b33@gmail.com \
--to=dsahern@gmail$(echo .)com \
--cc=aclaudi@redhat$(echo .)com \
--cc=dcaratti@redhat$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=stephen@networkplumber$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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