DPDK patches and discussions
 help / color / mirror / Atom feed
From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: Fan Zhang <roy.fan.zhang@intel.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] vhost/crypto: fix descriptor move
Date: Wed, 16 May 2018 08:11:14 +0200	[thread overview]
Message-ID: <ad1d2572-c88b-e3f6-c9f1-fcf760dfa152@redhat.com> (raw)
In-Reply-To: <20180509140839.85818-1-roy.fan.zhang@intel.com>

Hi Fan,

On 05/09/2018 04:08 PM, Fan Zhang wrote:
> This patch fixes the redundant descriptor move in the copy mode
> of vhost crypto. Originally the redundant descriptor move will
> cause the message parsing error.

As it is a fix, we need to specify which commit it fixes.
In this case it is:

Fixes: 3bb595ecd682 ("vhost/crypto: add request handler")

I'll add it when applying, no need to resubmit.

> Signed-off-by: Fan Zhang <roy.fan.zhang@intel.com>
> ---
>   lib/librte_vhost/vhost_crypto.c | 5 -----
>   1 file changed, 5 deletions(-)


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

Thanks,
Maxime

  reply	other threads:[~2018-05-16  6:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-09 14:08 Fan Zhang
2018-05-16  6:11 ` Maxime Coquelin [this message]
2018-05-16 10:54 ` 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=ad1d2572-c88b-e3f6-c9f1-fcf760dfa152@redhat.com \
    --to=maxime.coquelin@redhat.com \
    --cc=dev@dpdk.org \
    --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).