From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: "Stokes, Ian" <ian.stokes@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] [PATCH v2 1/1] cryptodev: fix build with Ofast.
Date: Thu, 19 Oct 2017 19:11:44 +0000 [thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D8976CC38047@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <CD7C01071941AC429549C17338DB8A5289178A7D@IRSMSX101.ger.corp.intel.com>
> -----Original Message-----
> From: Stokes, Ian
> Sent: Tuesday, October 17, 2017 4:17 PM
> To: De Lara Guarch, Pablo <pablo.de.lara.guarch@intel.com>;
> dev@dpdk.org
> Cc: stable@dpdk.org
> Subject: RE: [PATCH v2 1/1] cryptodev: fix build with Ofast.
>
> > > -----Original Message-----
> > > From: Stokes, Ian
> > > Sent: Tuesday, October 17, 2017 3:15 PM
> > > To: dev@dpdk.org
> > > Cc: De Lara Guarch, Pablo <pablo.de.lara.guarch@intel.com>; Stokes,
> > > Ian <ian.stokes@intel.com>
> > > Subject: [PATCH v2 1/1] cryptodev: fix build with Ofast.
> > >
> > > When compiling with an application that includes rte_cryptodev.h
> > > with Ofast, an error is reported regarding enumeration
> > > RTE_CRYPTO_OP_TYPE_UNDEFINED not handled in switch case in
> function
> > > __rte_crypto_op_reset().
> > >
> > > Fix this by adding a case for RTE_CRYPTO_OP_TYPE_UNDEFINED.
> > >
> > > Fixes: c0f87eb5252b ("cryptodev: change burst API to be crypto op
> > > oriented")
> > >
> > > Signed-off-by: Ian Stokes <ian.stokes@intel.com>
> >
> > Oh, and also CC stable :) I will do it for you.
>
> Apologies Pablo, thanks for this.
>
> Ian
> >
> > Acked-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
Applied to dpdk-next-crypto.
Thanks,
Pablo
prev parent reply other threads:[~2017-10-19 19:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1508249706-14827-1-git-send-email-ian.stokes@intel.com>
2017-10-17 15:13 ` De Lara Guarch, Pablo
2017-10-17 15:16 ` Stokes, Ian
2017-10-19 19:11 ` 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=E115CCD9D858EF4F90C690B0DCB4D8976CC38047@IRSMSX108.ger.corp.intel.com \
--to=pablo.de.lara.guarch@intel.com \
--cc=dev@dpdk.org \
--cc=ian.stokes@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).