From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Maxime Coquelin <maxime.coquelin@redhat.com>,
Fan Zhang <roy.fan.zhang@intel.com>,
dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] vhost/crypto: fix desc moving for copy mode
Date: Wed, 11 Apr 2018 18:36:55 +0100 [thread overview]
Message-ID: <e6d5b2f5-5c91-7ada-5546-7d1c426eea10@intel.com> (raw)
In-Reply-To: <14c6827f-a860-d563-d732-39ab097e8ac5@redhat.com>
On 4/11/2018 3:41 PM, Maxime Coquelin wrote:
>
>
> On 04/11/2018 12:09 PM, Fan Zhang wrote:
>> Fixes: cd39f8e4fd2a ("vhost/crypto: add request handler")
>>
>> This patch fixes the descriptor moving for copy mode by adding
>> the missing moving step after destination data parsing.
>>
>> Signed-off-by: Fan Zhang <roy.fan.zhang@intel.com>
>> ---
>> lib/librte_vhost/vhost_crypto.c | 9 +++++++++
>> 1 file changed, 9 insertions(+)
>
> Applied to dpdk-next-virtio/master
Squashed into relevant commit in next-net, thanks.
prev parent reply other threads:[~2018-04-11 17:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-11 10:09 Fan Zhang
2018-04-11 14:38 ` Maxime Coquelin
2018-04-11 14:41 ` Maxime Coquelin
2018-04-11 17:36 ` Ferruh Yigit [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=e6d5b2f5-5c91-7ada-5546-7d1c426eea10@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=maxime.coquelin@redhat.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).