DPDK patches and discussions
 help / color / mirror / Atom feed
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: "akhil.goyal@nxp.com" <akhil.goyal@nxp.com>
Subject: Re: [dpdk-dev] [PATCH] crypto/aesni_mb: fix compile
Date: Wed, 16 Jan 2019 16:48:48 +0000	[thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D89780366497@irsmsx112.ger.corp.intel.com> (raw)
In-Reply-To: <20190116132114.65674-1-roy.fan.zhang@intel.com>



> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Fan Zhang
> Sent: Wednesday, January 16, 2019 1:21 PM
> To: dev@dpdk.org
> Cc: akhil.goyal@nxp.com
> Subject: [dpdk-dev] [PATCH] crypto/aesni_mb: fix compile
> 
> This patch fixes the inflexible compile issue AESNI-MB PMD.
> Originally the compile of the PMD will fail if IPSec_MB is not installed in
> default location.
> 
> Fixes: c68d7aa354f6 ("crypto/aesni_mb: use architecture independent
> macros")
> 
> Signed-off-by: Fan Zhang <roy.fan.zhang@intel.com>
Acked-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>

  reply	other threads:[~2019-01-16 16:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-16 13:21 Fan Zhang
2019-01-16 16:48 ` De Lara Guarch, Pablo [this message]
2019-01-17 22:26 ` Thomas Monjalon
2019-01-18 10:57   ` Ananyev, Konstantin
2019-01-18 11:03     ` Thomas Monjalon
2019-01-18 11:55       ` Ananyev, Konstantin
2019-01-21 10:08         ` Zhang, Roy Fan
2019-01-21 15:56 ` [dpdk-dev] [PATCH v2] " Fan Zhang
2019-01-21 22:42   ` Ananyev, Konstantin
2019-01-22 16:29     ` 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=E115CCD9D858EF4F90C690B0DCB4D89780366497@irsmsx112.ger.corp.intel.com \
    --to=pablo.de.lara.guarch@intel.com \
    --cc=akhil.goyal@nxp.com \
    --cc=dev@dpdk.org \
    --cc=roy.fan.zhang@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).