From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Maxime Coquelin <maxime.coquelin@redhat.com>,
Fan Zhang <roy.fan.zhang@intel.com>,
dev@dpdk.org
Cc: stable@dpdk.org
Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH] doc: fix mismatch descriptorion
Date: Tue, 20 Nov 2018 12:28:39 +0000 [thread overview]
Message-ID: <e0542909-3553-6601-1a5c-d618fa27574d@intel.com> (raw)
In-Reply-To: <c3bc6159-6c03-af64-537c-c697852af423@redhat.com>
On 11/19/2018 9:49 AM, Maxime Coquelin wrote:
>
>
> On 11/19/18 10:38 AM, Fan Zhang wrote:
>> This patch fixes the mismatch keyword in vhost_crypto sample
>> application guide.
>>
>> Fixes: 709521f4c2cd ("examples/vhost_crypto: support multi-core")
>> Cc: stable@dpdk.org
>>
>> Signed-off-by: Fan Zhang <roy.fan.zhang@intel.com>
>> ---
>> doc/guides/sample_app_ug/vhost_crypto.rst | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/doc/guides/sample_app_ug/vhost_crypto.rst b/doc/guides/sample_app_ug/vhost_crypto.rst
>> index 3db57eab9..bbc25bde1 100644
>> --- a/doc/guides/sample_app_ug/vhost_crypto.rst
>> +++ b/doc/guides/sample_app_ug/vhost_crypto.rst
>> @@ -30,7 +30,7 @@ Start the vhost_crypto example
>>
>> ./vhost_crypto [EAL options] --
>> --config (lcore,cdev-id,queue-id)[,(lcore,cdev-id,queue-id)]
>> - --socketfile lcore,PATH
>> + --socket-file lcore,PATH
>> [--zero-copy]
>> [--guest-polling]
>>
>>
>
> Reviewed-by: Maxime Coquelin <maxime.coquelin@redhat.com>
>
Applied to dpdk-next-net/master, thanks.
(typo on title fixed while applying)
next prev parent reply other threads:[~2018-11-20 12:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-19 9:38 [dpdk-dev] " Fan Zhang
2018-11-19 9:49 ` Maxime Coquelin
2018-11-20 12:28 ` Ferruh Yigit [this message]
2018-11-20 12:30 ` [dpdk-dev] [dpdk-stable] " Maxime Coquelin
2018-11-19 10:28 ` [dpdk-dev] " Kovacevic, Marko
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=e0542909-3553-6601-1a5c-d618fa27574d@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=maxime.coquelin@redhat.com \
--cc=roy.fan.zhang@intel.com \
--cc=stable@dpdk.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).