From: Stephen Hemminger <stephen@networkplumber.org>
To: Mahesh Bandewar <mahesh@bandewar.net>
Cc: netdev <netdev@vger.kernel.org>, Mahesh Bandewar <maheshb@google.com>
Subject: Re: [PATCHv3 iproute2 0/2] clang + misc changes
Date: Thu, 30 Aug 2018 07:59:50 -0700 [thread overview]
Message-ID: <20180830075950.4e9563ae@xeon-e3> (raw)
In-Reply-To: <20180823010130.147780-1-mahesh@bandewar.net>
On Wed, 22 Aug 2018 18:01:30 -0700
Mahesh Bandewar <mahesh@bandewar.net> wrote:
> From: Mahesh Bandewar <maheshb@google.com>
>
> The primary theme is to make clang compile the iproute2 package without
> warnings. Along with this there are two other misc patches in the series.
>
> First patch uses the preferred_family when operating with maddr feature.
> Prior to this patch, it would always open an AF_INET socket irrespective
> of the family that is preferred via command-line.
>
> Second patch mostly adds format attributes to make the c-lang compiler
> happy and not throw the warning messages.
>
> Mahesh Bandewar (2):
> ipmaddr: use preferred_family when given
> iproute: make clang happy with iproute2 package
>
> include/json_writer.h | 3 +--
> ip/iplink_can.c | 19 ++++++++++++-------
> ip/ipmaddr.c | 13 ++++++++++++-
> lib/color.c | 1 +
> lib/json_print.c | 1 +
> lib/json_writer.c | 15 +--------------
> misc/ss.c | 3 ++-
> tc/m_ematch.c | 1 +
> tc/m_ematch.h | 1 +
> 9 files changed, 32 insertions(+), 25 deletions(-)
>
> --
> 2.18.0.1017.ga543ac7ca45-goog
>
Applied, thanks
prev parent reply other threads:[~2018-08-30 19:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-23 1:01 [PATCHv3 iproute2 0/2] clang + misc changes Mahesh Bandewar
2018-08-30 14:59 ` 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=20180830075950.4e9563ae@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=mahesh@bandewar.net \
--cc=maheshb@google.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).