DPDK patches and discussions
 help / color / mirror / Atom feed
From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: Ibtisam Tariq <ibtisam.tariq@emumba.com>, chenbo.xia@intel.com
Cc: dev@dpdk.org, roy.fan.zhang@intel.com
Subject: Re: [dpdk-dev] [PATCH] example/vhost_crypto: add new line character in usage
Date: Mon, 9 Nov 2020 10:11:40 +0100	[thread overview]
Message-ID: <85c6648a-4d53-6bc9-3f73-8e9d584b3904@redhat.com> (raw)
In-Reply-To: <20201102113825.5550-1-ibtisam.tariq@emumba.com>



On 11/2/20 12:38 PM, Ibtisam Tariq wrote:
> Add new line character(\n) in the usage of vhost_crypto example for
> better readability
> 
> Fixes: 709521f4c2c ("examples/vhost_crypto: support multi-core")
> Cc: roy.fan.zhang@intel.com
> 
> Signed-off-by: Ibtisam Tariq <ibtisam.tariq@emumba.com>
> ---
>  examples/vhost_crypto/main.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/examples/vhost_crypto/main.c b/examples/vhost_crypto/main.c
> index 11ad49159..29c8f7228 100644
> --- a/examples/vhost_crypto/main.c
> +++ b/examples/vhost_crypto/main.c
> @@ -195,7 +195,7 @@ vhost_crypto_usage(const char *prgname)
>  {
>  	printf("%s [EAL options] --\n"
>  		"  --%s <lcore>,SOCKET-FILE-PATH\n"
> -		"  --%s (lcore,cdev_id,queue_id)[,(lcore,cdev_id,queue_id)]"
> +		"  --%s (lcore,cdev_id,queue_id)[,(lcore,cdev_id,queue_id)]\n"
>  		"  --%s: zero copy\n"
>  		"  --%s: guest polling\n",
>  		prgname, SOCKET_FILE_KEYWORD, CONFIG_KEYWORD,
> 

Reviewed-by: Maxime Coquelin <maxime.coquelin@redhat.com>

Thanks,
Maxime


  parent reply	other threads:[~2020-11-09  9:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-02 11:38 Ibtisam Tariq
2020-11-05  8:56 ` David Marchand
2020-11-09  9:11 ` Maxime Coquelin [this message]
2020-11-09 16:32 ` Maxime Coquelin

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=85c6648a-4d53-6bc9-3f73-8e9d584b3904@redhat.com \
    --to=maxime.coquelin@redhat.com \
    --cc=chenbo.xia@intel.com \
    --cc=dev@dpdk.org \
    --cc=ibtisam.tariq@emumba.com \
    --cc=roy.fan.zhang@intel.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).