DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Hemant Agrawal <hemant.agrawal@nxp.com>
Cc: Akhil Goyal <akhil.goyal@nxp.com>,
	pablo.de.lara.guarch@intel.com, dev@dpdk.org,
	declan.doherty@intel.com
Subject: Re: [dpdk-dev] [PATCH v3] crypto/openssl: add openssl path for cross compile
Date: Thu, 12 Oct 2017 15:34:40 +0200	[thread overview]
Message-ID: <1673398.6HC6qXQKaP@xps> (raw)
In-Reply-To: <00e1e055-c2b4-9e41-5445-3e007010f3d1@nxp.com>

12/10/2017 15:31, Hemant Agrawal:
> On 10/12/2017 6:36 PM, Thomas Monjalon wrote:
> > 05/09/2017 11:02, Akhil Goyal:
> >> OPENSSL_PATH should be defined in case openssl
> >> driver is cross compiled
> >
> > No: in case OpenSSL cannot be found automatically,
> > you should use EXTRA_CFLAGS and EXTRA_LDFLAGS.
> >
> > It is the same for other standard dependencies like
> > libnuma, libpcap, libzip, etc.
> >
> Pablo/Thomas,
> 	We are ok to drop this patch.

OK, thanks a lot for confirming. Appreciated

  reply	other threads:[~2017-10-12 13:34 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-28 11:07 [dpdk-dev] [PATCH] config: add openssl in arm64-dpaa2-linuxapp-gcc Akhil Goyal
2017-07-28 11:07 ` [dpdk-dev] [PATCH] crypto/openssl: add openssl path for cross compile Akhil Goyal
2017-08-29  7:02   ` [dpdk-dev] [PATCH v2] " Akhil Goyal
2017-09-05  8:22     ` De Lara Guarch, Pablo
2017-09-05  8:37       ` Akhil Goyal
2017-09-05  9:02     ` [dpdk-dev] [PATCH v3] " Akhil Goyal
2017-09-06  9:26       ` De Lara Guarch, Pablo
2017-09-06 10:15       ` De Lara Guarch, Pablo
2017-10-12 13:06       ` Thomas Monjalon
2017-10-12 13:31         ` Hemant Agrawal
2017-10-12 13:34           ` Thomas Monjalon [this message]
2017-07-28 11:07 ` [dpdk-dev] [PATCH] crypto/openssl: performance improvements Akhil Goyal
2017-07-28 11:58   ` De Lara Guarch, Pablo
2017-07-28 12:02     ` Akhil Goyal
2017-07-28 12:07       ` De Lara Guarch, Pablo
2017-08-14 14:17   ` De Lara Guarch, Pablo
2017-08-15  6:44     ` Akhil Goyal
2017-08-15  7:26       ` De Lara Guarch, Pablo
2017-08-16  7:03         ` Akhil Goyal
2017-08-29  6:58   ` [dpdk-dev] [PATCH v2 1/2] crypto/openssl: replace evp APIs with HMAC APIs Akhil Goyal
2017-08-29  6:58     ` [dpdk-dev] [PATCH v2 2/2] crypto/openssl: performance improvements Akhil Goyal
2017-09-04 15:39       ` De Lara Guarch, Pablo
2017-09-05  5:57       ` [dpdk-dev] [PATCH v3 1/2] crypto/openssl: replace evp APIs with HMAC APIs Akhil Goyal
2017-09-05  5:57         ` [dpdk-dev] [PATCH v3 2/2] crypto/openssl: key and algo updated during session init Akhil Goyal
2017-09-06 10:24           ` De Lara Guarch, Pablo
2017-09-04 15:38     ` [dpdk-dev] [PATCH v2 1/2] crypto/openssl: replace evp APIs with HMAC APIs De Lara Guarch, Pablo
2017-09-08 14:03     ` De Lara Guarch, Pablo
2017-09-11  8:41       ` Akhil Goyal
2017-09-20  9:56       ` Akhil Goyal
2017-09-04 14:48 ` [dpdk-dev] [PATCH] config: add openssl in arm64-dpaa2-linuxapp-gcc De Lara Guarch, Pablo
2017-09-05  5:58   ` Akhil Goyal
2017-09-06 10:25     ` De Lara Guarch, Pablo
2017-10-12 13:01       ` Thomas Monjalon
2017-10-12 13:32         ` Hemant Agrawal

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=1673398.6HC6qXQKaP@xps \
    --to=thomas@monjalon.net \
    --cc=akhil.goyal@nxp.com \
    --cc=declan.doherty@intel.com \
    --cc=dev@dpdk.org \
    --cc=hemant.agrawal@nxp.com \
    --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).