From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: "Zhang, Roy Fan" <roy.fan.zhang@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v3] crypto/scheduler: fix session free
Date: Tue, 4 Apr 2017 15:27:04 +0000 [thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D89747802410@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <1491298268-119128-1-git-send-email-roy.fan.zhang@intel.com>
> -----Original Message-----
> From: Zhang, Roy Fan
> Sent: Tuesday, April 04, 2017 10:31 AM
> To: dev@dpdk.org
> Cc: De Lara Guarch, Pablo; stable@dpdk.org
> Subject: [PATCH v3] crypto/scheduler: fix session free
>
> This patch fixes the incorrection slave session free operation.
>
> Fixes: 57523e682bb7 ("crypto/scheduler: register operation functions")
>
> Signed-off-by: Fan Zhang <roy.fan.zhang@intel.com>
> ---
Acked and applied to dpdk-next-crypto.
Thanks,
Pablo
prev parent reply other threads:[~2017-04-04 15:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-03 15:47 [dpdk-dev] [PATCH] " Fan Zhang
2017-04-03 16:37 ` [dpdk-dev] [PATCH v2] " Fan Zhang
2017-04-04 9:31 ` [dpdk-dev] [PATCH v3] " Fan Zhang
2017-04-04 15:27 ` De Lara Guarch, Pablo [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=E115CCD9D858EF4F90C690B0DCB4D89747802410@IRSMSX108.ger.corp.intel.com \
--to=pablo.de.lara.guarch@intel.com \
--cc=dev@dpdk.org \
--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).