From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Akhil Goyal <akhil.goyal@nxp.com>,
Hemant Agrawal <hemant.agrawal@nxp.com>
Cc: dev@dpdk.org, "De Lara Guarch,
Pablo" <pablo.de.lara.guarch@intel.com>,
"Doherty, Declan" <declan.doherty@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2 0/2] cryptodev_start fixes
Date: Fri, 22 Jul 2016 12:41:06 +0200 [thread overview]
Message-ID: <1958912.KYcjeMgngt@xps13> (raw)
In-Reply-To: <E115CCD9D858EF4F90C690B0DCB4D8973C99F342@IRSMSX108.ger.corp.intel.com>
2016-07-22 10:20, De Lara Guarch, Pablo:
> From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
> > It seems cryptodev_start() calls empty driver functions,
> > and is not called in the example applications.
> >
> > This a v2 of patches from Hemant Agrawal and Akhil Goyal.
> > There are some improvements to make error messages more
> > consistent with existing ones and keep the existing error return.
> >
> > Are they important fixes for 16.07? Please advise.
> >
> > Hemant Agrawal (2):
> > examples/l2fwd-crypto: call start function
> > examples/ipsec-secgw: call start function
>
> Series-acked-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
Applied, thanks
prev parent reply other threads:[~2016-07-22 10:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-21 10:54 [dpdk-dev] [PATCH 1/2] example/l2fwd-crypto: add support for cryptodev_start Hemant Agrawal
2016-07-21 10:54 ` [dpdk-dev] [PATCH 2/2] example/ipsec-secgw: " Hemant Agrawal
2016-07-22 9:44 ` [dpdk-dev] [PATCH v2 0/2] cryptodev_start fixes Thomas Monjalon
2016-07-22 9:44 ` [dpdk-dev] [PATCH v2 1/2] examples/l2fwd-crypto: call start function Thomas Monjalon
2016-07-22 9:44 ` [dpdk-dev] [PATCH v2 2/2] examples/ipsec-secgw: " Thomas Monjalon
2016-07-22 10:20 ` [dpdk-dev] [PATCH v2 0/2] cryptodev_start fixes De Lara Guarch, Pablo
2016-07-22 10:41 ` Thomas Monjalon [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=1958912.KYcjeMgngt@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=akhil.goyal@nxp.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=pablo.de.lara.guarch@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).