DPDK patches and discussions
 help / color / mirror / Atom feed
From: Brian Dooley <brian.dooley@intel.com>
To: Kai Ji <kai.ji@intel.com>
Cc: dev@dpdk.org, gakhil@marvell.com,
	Brian Dooley <brian.dooley@intel.com>,
	kevin.osullivan@intel.com
Subject: [PATCH v2 2/2] common/qat: change define header
Date: Thu,  6 Jul 2023 16:04:54 +0000	[thread overview]
Message-ID: <20230706160454.479229-3-brian.dooley@intel.com> (raw)
In-Reply-To: <20230706160454.479229-1-brian.dooley@intel.com>

change define from RTE_LIB_SECURITY to BUILD_QAT_SYM as
RTE_ETHER_CRC_LEN value is protected by BUILD_QAT_SYM.

Fixes: ce7a737c8f02 ("crypto/qat: support cipher-CRC offload")
Cc: kevin.osullivan@intel.com

Signed-off-by: Brian Dooley <brian.dooley@intel.com>
---
 drivers/common/qat/qat_qp.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/common/qat/qat_qp.c b/drivers/common/qat/qat_qp.c
index 094d684abc..f284718441 100644
--- a/drivers/common/qat/qat_qp.c
+++ b/drivers/common/qat/qat_qp.c
@@ -11,7 +11,7 @@
 #include <bus_pci_driver.h>
 #include <rte_atomic.h>
 #include <rte_prefetch.h>
-#ifdef RTE_LIB_SECURITY
+#ifdef BUILD_QAT_SYM
 #include <rte_ether.h>
 #endif
 
-- 
2.25.1


  parent reply	other threads:[~2023-07-06 16:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-06 13:15 [PATCH v1] crypto/ipsec_mb: remove unused defines Brian Dooley
2023-07-06 16:04 ` [PATCH v2 0/2] " Brian Dooley
2023-07-06 16:04   ` [PATCH v2 1/2] crypto/ipsec_mb: " Brian Dooley
2023-07-06 16:14     ` Power, Ciara
2023-07-06 16:04   ` Brian Dooley [this message]
2023-07-06 16:12     ` [PATCH v2 2/2] common/qat: change define header Power, Ciara
2023-07-06 16:21   ` [PATCH v3 0/2] remove unused defines Brian Dooley
2023-07-06 16:21     ` [PATCH v3 1/2] crypto/ipsec_mb: " Brian Dooley
2023-07-07 11:38       ` Maxime Coquelin
2023-07-06 16:21     ` [PATCH v3 2/2] common/qat: change define header Brian Dooley
2023-07-06 18:31     ` [EXT] [PATCH v3 0/2] remove unused defines Akhil Goyal

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=20230706160454.479229-3-brian.dooley@intel.com \
    --to=brian.dooley@intel.com \
    --cc=dev@dpdk.org \
    --cc=gakhil@marvell.com \
    --cc=kai.ji@intel.com \
    --cc=kevin.osullivan@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).