From: Gagandeep Singh <G.Singh@nxp.com>
To: "dev@dpdk.org" <dev@dpdk.org>, Akhil Goyal <akhil.goyal@nxp.com>
Cc: Gagandeep Singh <G.Singh@nxp.com>
Subject: [dpdk-dev] [PATCH] crypto/caam_jr: fix redefinition error
Date: Tue, 23 Oct 2018 11:54:00 +0000 [thread overview]
Message-ID: <20181023115322.16134-1-g.singh@nxp.com> (raw)
dma_addr_t is already defined in compat.h.
so removing the local definition from caam_jr_config.h
Fixes: b70a67ab70 ("crypto/caam_jr: add HW tuning options")
Signed-off-by: Gagandeep Singh <g.singh@nxp.com>
---
drivers/crypto/caam_jr/caam_jr_config.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/crypto/caam_jr/caam_jr_config.h b/drivers/crypto/caam_jr/caam_jr_config.h
index e7855cee6..041187a84 100644
--- a/drivers/crypto/caam_jr/caam_jr_config.h
+++ b/drivers/crypto/caam_jr/caam_jr_config.h
@@ -7,6 +7,8 @@
#include <rte_byteorder.h>
+#include <compat.h>
+
#ifdef RTE_LIBRTE_PMD_CAAM_JR_BE
#define CAAM_BYTE_ORDER __BIG_ENDIAN
#else
@@ -19,8 +21,6 @@
#define CORE_BYTE_ORDER __LITTLE_ENDIAN
#endif
-typedef uint64_t dma_addr_t;
-
#if CORE_BYTE_ORDER != CAAM_BYTE_ORDER
#define cpu_to_caam64 rte_cpu_to_be_64
--
2.17.1
next reply other threads:[~2018-10-23 11:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-23 11:54 Gagandeep Singh [this message]
2018-10-24 20:41 ` 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=20181023115322.16134-1-g.singh@nxp.com \
--to=g.singh@nxp.com \
--cc=akhil.goyal@nxp.com \
--cc=dev@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).