From: Thomas Monjalon <thomas@monjalon.net>
To: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>
Cc: "Zhang, Roy Fan" <roy.fan.zhang@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"akhil.goyal@nxp.com" <akhil.goyal@nxp.com>,
"De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
Subject: Re: [PATCH] crypto/aesni_mb: fix compile
Date: Fri, 18 Jan 2019 12:03:20 +0100 [thread overview]
Message-ID: <4850125.tHd5LTnENi@xps> (raw)
In-Reply-To: <2601191342CEEE43887BDE71AB977258010D905841@irsmsx105.ger.corp.intel.com>
18/01/2019 11:57, Ananyev, Konstantin:
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Thomas Monjalon
> > 16/01/2019 14:21, Fan Zhang:
> > > 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>
> > > ---
> > > -IMB_HDR = /usr/include/intel-ipsec-mb.h
> > > +IMB_HDR = $(shell echo "\#include <intel-ipsec-mb.h>" | \
> >
> > What is the backslash? Looks like a typo.
>
> Wouldn't make get confused without it?
Confused about what?
I tested without backslash, it works.
next prev parent reply other threads:[~2019-01-18 11:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-16 13:21 [PATCH] crypto/aesni_mb: fix compile Fan Zhang
2019-01-16 16:48 ` De Lara Guarch, Pablo
2019-01-17 22:26 ` Thomas Monjalon
2019-01-18 10:57 ` Ananyev, Konstantin
2019-01-18 11:03 ` Thomas Monjalon [this message]
2019-01-18 11:55 ` Ananyev, Konstantin
2019-01-21 10:08 ` Zhang, Roy Fan
2019-01-21 15:56 ` [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=4850125.tHd5LTnENi@xps \
--to=thomas@monjalon.net \
--cc=akhil.goyal@nxp.com \
--cc=dev@dpdk.org \
--cc=konstantin.ananyev@intel.com \
--cc=pablo.de.lara.guarch@intel.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.