From: David Christensen <drc@linux.vnet.ibm.com>
To: rosen.xu@intel.com, grive@u256.net
Cc: dev@dpdk.org, David Christensen <drc@linux.vnet.ibm.com>,
bruce.richardson@intel.com
Subject: [dpdk-dev] [PATCH] pci: restore access to RTE_VERIFY for Power builds
Date: Mon, 16 Mar 2020 13:47:49 -0700 [thread overview]
Message-ID: <20200316204749.28066-1-drc@linux.vnet.ibm.com> (raw)
The include file rte_debug.h is pulled into x86 builds through the
following callchain:
lib/librte_eal/common/include/generic/rte_cycles.h:17,
lib/librte_eal/common/include/arch/x86/rte_cycles.h:13,
lib/librte_eal/common/include/arch/x86/rte_spinlock.h:18,
lib/librte_eal/common/include/arch/x86/rte_rwlock.h:13,
The PPC specific version of the same callchain does not include
rte_debug.h. Add rte_debug.h back into the C files that require it.
Fixes: 0dcba5256287 ("pci: remove unneeded includes in public header file")
Cc: bruce.richardson@intel.com
Signed-off-by: David Christensen <drc@linux.vnet.ibm.com>
---
drivers/bus/ifpga/ifpga_bus.c | 1 +
lib/librte_pci/rte_pci.c | 1 +
2 files changed, 2 insertions(+)
diff --git a/drivers/bus/ifpga/ifpga_bus.c b/drivers/bus/ifpga/ifpga_bus.c
index dfd6b1fba..addbc3e86 100644
--- a/drivers/bus/ifpga/ifpga_bus.c
+++ b/drivers/bus/ifpga/ifpga_bus.c
@@ -24,6 +24,7 @@
#include <rte_kvargs.h>
#include <rte_alarm.h>
#include <rte_string_fns.h>
+#include <rte_debug.h>
#include "rte_rawdev.h"
#include "rte_rawdev_pmd.h"
diff --git a/lib/librte_pci/rte_pci.c b/lib/librte_pci/rte_pci.c
index a753cf3ec..d1ab6b414 100644
--- a/lib/librte_pci/rte_pci.c
+++ b/lib/librte_pci/rte_pci.c
@@ -20,6 +20,7 @@
#include <rte_eal.h>
#include <rte_string_fns.h>
#include <rte_common.h>
+#include <rte_debug.h>
#include "rte_pci.h"
--
2.18.1
next reply other threads:[~2020-03-16 20:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-16 20:47 David Christensen [this message]
2020-03-16 23:14 ` dwilder
2020-03-17 13:21 ` David Marchand
2020-03-17 19:39 ` David Marchand
2020-03-19 1:26 ` Xu, Rosen
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=20200316204749.28066-1-drc@linux.vnet.ibm.com \
--to=drc@linux.vnet.ibm.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=grive@u256.net \
--cc=rosen.xu@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).