DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [pull-request] next-crypto 18.02 rc1
Date: Sat, 20 Jan 2018 21:41:38 +0100	[thread overview]
Message-ID: <6362820.kChM4fuPcs@xps> (raw)
In-Reply-To: <E115CCD9D858EF4F90C690B0DCB4D8976CC75B14@IRSMSX108.ger.corp.intel.com>

20/01/2018 19:19, De Lara Guarch, Pablo:
> Hi Thomas,
> 
> From: Thomas Monjalon [mailto:thomas@monjalon.net]
> > 20/01/2018 16:15, Pablo de Lara:
> > >   http://dpdk.org/git/next/dpdk-next-crypto
> > 
> > There is a compilation error with clang:
> > 
> > drivers/crypto/aesni_mb/rte_aesni_mb_pmd_private.h:46:4: fatal error:
> > use of undeclared identifier 'AES_CCM'
> 
> There is a new version of the Multi buffer library. I sent a patch that updated the documentation.
> You need to get version 0.48.

Thank you, I always forget to update these crypto libraries when pulling.

  reply	other threads:[~2018-01-20 20:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-20 15:15 Pablo de Lara
2018-01-20 17:00 ` Thomas Monjalon
2018-01-20 18:19   ` De Lara Guarch, Pablo
2018-01-20 20:41     ` Thomas Monjalon [this message]
2018-01-21  9:42 ` Thomas Monjalon

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=6362820.kChM4fuPcs@xps \
    --to=thomas@monjalon.net \
    --cc=dev@dpdk.org \
    --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).