From: Thomas Monjalon <thomas@monjalon.net>
To: dev@dpdk.org
Cc: Kai Ji <kai.ji@intel.com>,
Pablo de Lara <pablo.de.lara.guarch@intel.com>,
Bruce Richardson <bruce.richardson@intel.com>,
Konstantin Ananyev <konstantin.ananyev@huawei.com>,
Vladimir Medvedkin <vladimir.medvedkin@intel.com>,
Yipeng Wang <yipeng1.wang@intel.com>,
Sameh Gobriel <sameh.gobriel@intel.com>
Subject: [PATCH] eal/x86: remove useless include from spinlock header
Date: Fri, 19 Sep 2025 21:02:26 +0200 [thread overview]
Message-ID: <20250919190226.1840008-1-thomas@monjalon.net> (raw)
rte_cpuflags.h is not used in rte_spinlock.h,
so it is removed, and added back in .c files where needed.
Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
---
drivers/crypto/ipsec_mb/ipsec_mb_private.c | 1 +
lib/eal/x86/include/rte_spinlock.h | 1 -
lib/eal/x86/rte_power_intrinsics.c | 1 +
lib/fib/trie.c | 1 +
lib/member/rte_member_ht.c | 1 +
lib/member/rte_member_sketch.c | 1 +
6 files changed, 5 insertions(+), 1 deletion(-)
diff --git a/drivers/crypto/ipsec_mb/ipsec_mb_private.c b/drivers/crypto/ipsec_mb/ipsec_mb_private.c
index 0d2538832d..b4c36e7f58 100644
--- a/drivers/crypto/ipsec_mb/ipsec_mb_private.c
+++ b/drivers/crypto/ipsec_mb/ipsec_mb_private.c
@@ -5,6 +5,7 @@
#include <bus_vdev_driver.h>
#include <rte_common.h>
#include <rte_cryptodev.h>
+#include <rte_cpuflags.h>
#include <rte_errno.h>
#include "ipsec_mb_private.h"
diff --git a/lib/eal/x86/include/rte_spinlock.h b/lib/eal/x86/include/rte_spinlock.h
index a14da41964..273bbdc39c 100644
--- a/lib/eal/x86/include/rte_spinlock.h
+++ b/lib/eal/x86/include/rte_spinlock.h
@@ -7,7 +7,6 @@
#include "generic/rte_spinlock.h"
#include "rte_rtm.h"
-#include "rte_cpuflags.h"
#include "rte_branch_prediction.h"
#include "rte_common.h"
#include "rte_pause.h"
diff --git a/lib/eal/x86/rte_power_intrinsics.c b/lib/eal/x86/rte_power_intrinsics.c
index 1cb2e908c0..489ad3983f 100644
--- a/lib/eal/x86/rte_power_intrinsics.c
+++ b/lib/eal/x86/rte_power_intrinsics.c
@@ -10,6 +10,7 @@
#include <rte_lcore_var.h>
#include <rte_rtm.h>
#include <rte_spinlock.h>
+#include <rte_cpuflags.h>
#include "rte_power_intrinsics.h"
diff --git a/lib/fib/trie.c b/lib/fib/trie.c
index 24a08b827d..ff4c750952 100644
--- a/lib/fib/trie.c
+++ b/lib/fib/trie.c
@@ -8,6 +8,7 @@
#include <rte_debug.h>
#include <rte_malloc.h>
+#include <rte_cpuflags.h>
#include <rte_errno.h>
#include <rte_rib6.h>
diff --git a/lib/member/rte_member_ht.c b/lib/member/rte_member_ht.c
index 738471b378..8c89a949c8 100644
--- a/lib/member/rte_member_ht.c
+++ b/lib/member/rte_member_ht.c
@@ -8,6 +8,7 @@
#include <rte_random.h>
#include <rte_log.h>
#include <rte_vect.h>
+#include <rte_cpuflags.h>
#include "member.h"
#include "rte_member.h"
diff --git a/lib/member/rte_member_sketch.c b/lib/member/rte_member_sketch.c
index 15af6786e9..b753bac1bd 100644
--- a/lib/member/rte_member_sketch.c
+++ b/lib/member/rte_member_sketch.c
@@ -12,6 +12,7 @@
#include <rte_log.h>
#include <rte_random.h>
#include <rte_prefetch.h>
+#include <rte_cpuflags.h>
#include <rte_ring_elem.h>
#include "member.h"
--
2.51.0
reply other threads:[~2025-09-19 19:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20250919190226.1840008-1-thomas@monjalon.net \
--to=thomas@monjalon.net \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=kai.ji@intel.com \
--cc=konstantin.ananyev@huawei.com \
--cc=pablo.de.lara.guarch@intel.com \
--cc=sameh.gobriel@intel.com \
--cc=vladimir.medvedkin@intel.com \
--cc=yipeng1.wang@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).