DPDK patches and discussions
 help / color / mirror / Atom feed
From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v3] cryptodev: add capabilities discovery mechanism
Date: Fri, 11 Mar 2016 01:31:12 +0000	[thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D8973C8C874F@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <16034076.SnoENOFo98@xps13>



> -----Original Message-----
> From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
> Sent: Friday, March 11, 2016 1:20 AM
> To: De Lara Guarch, Pablo
> Cc: dev@dpdk.org
> Subject: Re: [dpdk-dev] [PATCH v3] cryptodev: add capabilities discovery
> mechanism
> 
> There is a clang error here:
> 
> > +static const struct rte_cryptodev_capabilities
> aesni_gcm_pmd_capabilities[] = {
> 
> drivers/crypto/aesni_gcm/aesni_gcm_pmd_ops.c:41:48: fatal error:
> 	unused variable 'aesni_gcm_pmd_capabilities'

Nice catch. Submitting a v4 shortly...

  reply	other threads:[~2016-03-11  1:31 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-30 13:10 [dpdk-dev] [PATCH] " Declan Doherty
2016-02-02 17:38 ` De Lara Guarch, Pablo
2016-02-10 16:37 ` Trahe, Fiona
2016-03-10 17:07 ` [dpdk-dev] [PATCH v2] " Pablo de Lara
2016-03-10 19:54   ` [dpdk-dev] [PATCH v3] " Pablo de Lara
2016-03-10 21:27     ` Trahe, Fiona
2016-03-11  1:20     ` Thomas Monjalon
2016-03-11  1:31       ` De Lara Guarch, Pablo [this message]
2016-03-11  1:36     ` [dpdk-dev] [PATCH v4] " Pablo de Lara
2016-03-11  9:35       ` Thomas Monjalon
2016-03-14  8:13       ` Cao, Min
2016-03-14  8:25     ` [dpdk-dev] [PATCH v3] " Cao, Min
2016-03-14  8:26   ` [dpdk-dev] [PATCH v2] " Cao, Min

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=E115CCD9D858EF4F90C690B0DCB4D8973C8C874F@IRSMSX108.ger.corp.intel.com \
    --to=pablo.de.lara.guarch@intel.com \
    --cc=dev@dpdk.org \
    --cc=thomas.monjalon@6wind.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).