From: "Dooley, Brian" <brian.dooley@intel.com>
To: "Power, Ciara" <ciara.power@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "stable@dpdk.org" <stable@dpdk.org>, "Ji, Kai" <kai.ji@intel.com>
Subject: RE: [PATCH] crypto/qat: fix build when no openssl exists
Date: Tue, 31 Oct 2023 08:54:32 +0000 [thread overview]
Message-ID: <SJ0PR11MB5056D553786885192C9993F483A0A@SJ0PR11MB5056.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20231027142305.2328017-1-ciara.power@intel.com>
Hi Ciara,
> -----Original Message-----
> From: Power, Ciara <ciara.power@intel.com>
> Sent: Friday, October 27, 2023 3:23 PM
> To: dev@dpdk.org
> Cc: Power, Ciara <ciara.power@intel.com>; Dooley, Brian
> <brian.dooley@intel.com>; stable@dpdk.org; Ji, Kai <kai.ji@intel.com>
> Subject: [PATCH] crypto/qat: fix build when no openssl exists
>
> Previously some compilation errors existed when no openssl was installed on
> the system, and intel-ipsec-mb was installed, due to missing headers and
> macros.
>
> This patch fixes the issue by adding in extra ifdefs around openssl specific code
> paths, and by adding the relevant macros explicitly in QAT code so it does not
> depend on openssl at all.
>
> Fixes: ca0ba0e48129 ("crypto/qat: default to IPsec MB for computations")
> Cc: brian.dooley@intel.com
> Cc: stable@dpdk.org
>
> Signed-off-by: Ciara Power <ciara.power@intel.com>
Thanks!
Acked-by: Brian Dooley <brian.dooley@intel.com>
prev parent reply other threads:[~2023-10-31 8:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-27 14:23 Ciara Power
2023-10-27 15:55 ` Ji, Kai
2023-10-30 7:18 ` [EXT] " Akhil Goyal
2023-10-31 8:54 ` Dooley, Brian [this message]
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=SJ0PR11MB5056D553786885192C9993F483A0A@SJ0PR11MB5056.namprd11.prod.outlook.com \
--to=brian.dooley@intel.com \
--cc=ciara.power@intel.com \
--cc=dev@dpdk.org \
--cc=kai.ji@intel.com \
--cc=stable@dpdk.org \
/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).