From: Stephen Hemminger <stephen@networkplumber.org>
To: alin.nastac@gmail.com
Cc: netdev@vger.kernel.org, Stephen Hemminger <stephen@networkplumber.org>
Subject: [RFC iproute 0/5] print_uint issues
Date: Fri, 20 Apr 2018 10:15:14 -0700 [thread overview]
Message-ID: <20180420171519.8028-1-stephen@networkplumber.org> (raw)
There are several issues with implicit conversions in json
handling print_uint function which were first seen and patches
proposed by Alin Nastac. This is my swipe at them.
Final version will be some combination of his patches and
some of this.
Spotted some more changing print_uint into a macro,
but that got ugly.
Stephen Hemminger (5):
ipneigh: fix missing format specifier
json: make json print_uint take unsigned int
flower: use 16 bit format where possible
tcp_metrics: use print_luint
mroute: use print_uint64
include/json_print.h | 16 +++++++++++++---
ip/ipmroute.c | 10 +++++-----
ip/ipneigh.c | 2 +-
ip/tcp_metrics.c | 2 +-
lib/json_print.c | 33 ++++++++++++++++++++++++++++++---
tc/f_flower.c | 2 +-
6 files changed, 51 insertions(+), 14 deletions(-)
--
2.17.0
next reply other threads:[~2018-04-20 17:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-20 17:15 Stephen Hemminger [this message]
2018-04-20 17:15 ` [RFC iproute 1/5] ipneigh: fix missing format specifier Stephen Hemminger
2018-04-20 17:15 ` [RFC iproute 2/5] json: make json print_uint take unsigned int Stephen Hemminger
2018-04-20 17:15 ` [RFC iproute 3/5] flower: use 16 bit format where possible Stephen Hemminger
2018-04-20 17:15 ` [RFC iproute 4/5] tcp_metrics: use print_luint Stephen Hemminger
2018-04-20 17:15 ` [RFC iproute 5/5] mroute: use print_uint64 Stephen Hemminger
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=20180420171519.8028-1-stephen@networkplumber.org \
--to=stephen@networkplumber.org \
--cc=alin.nastac@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.