netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Serhey Popovych <serhe.popovych@gmail.com>
To: netdev@vger.kernel.org
Subject: Re: [PATCH iproute2-next v2 0/3] ip/tunnel: Unify tunnel help message print routines
Date: Fri, 9 Feb 2018 09:00:14 +0200	[thread overview]
Message-ID: <550674c8-5599-1e59-f1d4-cad87ae7b4ea@gmail.com> (raw)
In-Reply-To: <1518158702-32604-1-git-send-email-serhe.popovych@gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 2141 bytes --]

> To show only relevant diffs of ip and ipv6 variants help message print
> routines needs to be unified and improved.
> 
> Get rid of print_usage() and usage() wrappers: use single function to
> output help message. As side effect we return -1 from parse function
> instead of calling exit(2) in case of "... tunnel <help|garbage>" is
> found.
> 
> Additionally we get pointer to @struct link_util and can directly access
> ->id information to prepare customized help message.
> 
> Split calls to fprintf() two group: one that contains format string with
> specifiers (thus requiring parameters) and another one that does not.
> This helps compiler to optimize calls to fprintf() with fputs() when no
> format specifiers in string. Do not use fputs() directly to keep code
> formatting nice.
> 
> After this series applied following diffs:
> 
>   # diff -urN ip/link_gre{,6}.c
>   # diff -urN ip/link_vti{,6}.c
>   # diff -urN ip/link_ip{,6}tnl.c
> 
> in scope of help print routines reduced to necessary minimum.
> 
> Tested minimally by compiling and executing "ip link help <kind>" and
> "ip link add type help" commands. Looks correct.
> 
> See individual patch description for more information.
> 
> Reviews, commands and suggestions are welcome.
> 
> v2
>   Dropped function prefix changes from the series: this is not strictly
>   relared change and should be done separately.

There is v3 available, we have checkpatch and commit description
problems here.

> 
> Thanks,
> Serhii
> 
> Serhey Popovych (3):
>   vti/vti6: Unify vti_print_help()
>   gre/gre6: Unify gre_print_help()
>   iptnl/ip6tnl: Unify iptunnel_print_help()
> 
>  ip/link_gre.c    |   73 ++++++++++++++++++++------------------------
>  ip/link_gre6.c   |   74 +++++++++++++++++++++------------------------
>  ip/link_ip6tnl.c |   45 ++++++++++++++--------------
>  ip/link_iptnl.c  |   88 ++++++++++++++++++++++++++----------------------------
>  ip/link_vti.c    |   42 +++++++++++---------------
>  ip/link_vti6.c   |   33 +++++++++-----------
>  6 files changed, 165 insertions(+), 190 deletions(-)
> 



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 490 bytes --]

      parent reply	other threads:[~2018-02-09  7:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-09  6:44 [PATCH iproute2-next v2 0/3] ip/tunnel: Unify tunnel help message print routines Serhey Popovych
2018-02-09  6:45 ` [PATCH iproute2-next v2 1/3] vti/vti6: Unify vti_print_help() Serhey Popovych
2018-02-09  6:45 ` [PATCH iproute2-next v2 2/3] gre/gre6: Unify gre_print_help() Serhey Popovych
2018-02-09  6:45 ` [PATCH iproute2-next v2 3/3] iptnl/ip6tnl: Unify iptunnel_print_help() Serhey Popovych
2018-02-09  7:00 ` Serhey Popovych [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=550674c8-5599-1e59-f1d4-cad87ae7b4ea@gmail.com \
    --to=serhe.popovych@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 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).