DPDK patches and discussions
 help / color / mirror / Atom feed
From: Radu Nicolau <radu.nicolau@intel.com>
To: Anoob Joseph <anoob.joseph@caviumnetworks.com>,
	Akhil Goyal <akhil.goyal@nxp.com>,
	Declan Doherty <declan.doherty@intel.com>
Cc: Jerin Jacob <jerin.jacob@caviumnetworks.com>,
	Narayana Prasad <narayanaprasad.athreya@caviumnetworks.com>,
	dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] examples/ipsec-secgw: fix usage print
Date: Tue, 17 Apr 2018 10:02:06 +0100	[thread overview]
Message-ID: <f624a6e4-f646-0f0f-0fdc-61b5c5bb4e6d@intel.com> (raw)
In-Reply-To: <1523881395-32127-1-git-send-email-anoob.joseph@caviumnetworks.com>


On 4/16/2018 1:23 PM, Anoob Joseph wrote:
> The usage print was not updated when jumbo frames & crypto_dev mask
> support was added. Fixing that. Also, the optional arguments were not
> properly highlighted in the usage header. This is also fixed.
>
> General cleanup of the usage print was also done to make it look more
> cleaner and similar to what is existing in other applications like
> l3fwd.
>
> Fixes: bbabfe6e4ee4 ("examples/ipsec_secgw: support jumbo frames")
> Fixes: 2c68fe791538 ("examples/ipsec-secgw: add cryptodev mask option")
> Fixes: d299106e8e31 ("examples/ipsec-secgw: add IPsec sample application")
>
> Signed-off-by: Anoob Joseph <anoob.joseph@caviumnetworks.com>
> ---
>
Acked-by: Radu Nicolau <radu.nicolau@intel.com> 
<mailto:radu.nicolau@intel.com>

  reply	other threads:[~2018-04-17  9:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-16 12:23 Anoob Joseph
2018-04-17  9:02 ` Radu Nicolau [this message]
2018-04-18 10:25   ` De Lara Guarch, Pablo

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=f624a6e4-f646-0f0f-0fdc-61b5c5bb4e6d@intel.com \
    --to=radu.nicolau@intel.com \
    --cc=akhil.goyal@nxp.com \
    --cc=anoob.joseph@caviumnetworks.com \
    --cc=declan.doherty@intel.com \
    --cc=dev@dpdk.org \
    --cc=jerin.jacob@caviumnetworks.com \
    --cc=narayanaprasad.athreya@caviumnetworks.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).