From: Stephen Hemminger <stephen@networkplumber.org>
To: dsahern@gmail.com
Cc: netdev@vger.kernel.org, Stephen Hemminger <sthemmin@microsoft.com>
Subject: [PATCH iproute2-next 0/3] route code cleanups
Date: Wed, 7 Feb 2018 16:25:03 -0800 [thread overview]
Message-ID: <20180208002506.14272-1-sthemmin@microsoft.com> (raw)
Make code in iproute conform more to current coding style
conventions. Also split flush out into separate function.
Stephen Hemminger (3):
iproute: whitespace fixes
iproute: don't do assignment in condition
iproute: make flush a separate function
ip/iproute.c | 165 ++++++++++++++++++++++++++++++++---------------------------
1 file changed, 91 insertions(+), 74 deletions(-)
--
2.15.1
next reply other threads:[~2018-02-08 0:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-08 0:25 Stephen Hemminger [this message]
2018-02-08 0:25 ` [PATCH iproute2-next 1/3] iproute: whitespace fixes Stephen Hemminger
2018-02-08 0:25 ` [PATCH iproute2-next 2/3] iproute: don't do assignment in condition Stephen Hemminger
2018-02-08 0:25 ` [PATCH iproute2-next 3/3] iproute: make flush a separate function Stephen Hemminger
2018-02-08 0:29 ` [PATCH iproute2-next 0/3] route code cleanups David Ahern
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=20180208002506.14272-1-sthemmin@microsoft.com \
--to=stephen@networkplumber.org \
--cc=dsahern@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=sthemmin@microsoft.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 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.