From: David Ahern <dsahern@gmail.com>
To: Serhey Popovych <serhe.popovych@gmail.com>, netdev@vger.kernel.org
Subject: Re: [PATCH iproute2-next] ip: Use print_0xhex() where appropriate
Date: Fri, 9 Feb 2018 09:12:41 -0700 [thread overview]
Message-ID: <ad39e229-f19e-7121-4c19-bf06aff751b1@gmail.com> (raw)
In-Reply-To: <1518105845-4951-1-git-send-email-serhe.popovych@gmail.com>
On 2/8/18 9:04 AM, Serhey Popovych wrote:
> In gre/gre6 for non-JSON output 0x%x format is used: use print_0xhex()
> to get the same value for JSON.
>
> Get rid of custom _print_hex() in bridge slave code: print_0xhex() can
> be used perfectly.
>
> Break long print_uint() with long argument list to fit into 80 columns.
>
> Signed-off-by: Serhey Popovych <serhe.popovych@gmail.com>
> ---
> ip/iplink_bridge_slave.c | 24 +++++-------------------
> ip/link_gre.c | 6 ++++--
> ip/link_gre6.c | 6 ++++--
> 3 files changed, 13 insertions(+), 23 deletions(-)
>
applied to iproute2-next
prev parent reply other threads:[~2018-02-09 16:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-08 16:04 [PATCH iproute2-next] ip: Use print_0xhex() where appropriate Serhey Popovych
2018-02-09 16:12 ` 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=ad39e229-f19e-7121-4c19-bf06aff751b1@gmail.com \
--to=dsahern@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=serhe.popovych@gmail.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).