From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: Fan Zhang <roy.fan.zhang@intel.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] examples/vhost_crypto: fix session private mempool
Date: Thu, 17 Jan 2019 12:34:47 +0100 [thread overview]
Message-ID: <2351b88e-0676-bd15-c421-9fd642f6e1e8@redhat.com> (raw)
In-Reply-To: <20190115103808.76222-1-roy.fan.zhang@intel.com>
On 1/15/19 11:38 AM, Fan Zhang wrote:
> This patch fixes the incorrect session private mempool passing
> to cryptodev.
>
> Fixes: ac5e42daca19 ("vhost/crypto: use separate session mempools")
>
> Signed-off-by: Fan Zhang <roy.fan.zhang@intel.com>
> ---
> examples/vhost_crypto/main.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
Applied to dpdk-next-virtio/master.
Thanks,
Maxime
prev parent reply other threads:[~2019-01-17 11:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-15 10:38 Fan Zhang
2019-01-16 12:02 ` De Lara Guarch, Pablo
2019-01-17 8:32 ` Maxime Coquelin
2019-01-17 11:34 ` Maxime Coquelin [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=2351b88e-0676-bd15-c421-9fd642f6e1e8@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).