From: Weiguo Li <liwg06@foxmail.com>
To: dev@dpdk.org
Subject: [PATCH v2 11/16] kni: add define guards to avoid multi-inclusion
Date: Wed, 9 Feb 2022 11:02:19 +0800 [thread overview]
Message-ID: <tencent_F64448E9987C8F8DD08B44C47CF22C9E320A@qq.com> (raw)
In-Reply-To: <cover.1644374873.git.liwg06@foxmail.com>
Supplement define guards to prevent multiple inclusion.
Signed-off-by: Weiguo Li <liwg06@foxmail.com>
---
kernel/linux/kni/compat.h | 5 +++++
lib/kni/rte_kni_fifo.h | 5 ++++-
2 files changed, 9 insertions(+), 1 deletion(-)
diff --git a/kernel/linux/kni/compat.h b/kernel/linux/kni/compat.h
index 664785674f..f15c66df26 100644
--- a/kernel/linux/kni/compat.h
+++ b/kernel/linux/kni/compat.h
@@ -3,6 +3,9 @@
* Minimal wrappers to allow compiling kni on older kernels.
*/
+#ifndef KNI_COMPAT_H
+#define KNI_COMPAT_H
+
#include <linux/version.h>
#ifndef RHEL_RELEASE_VERSION
@@ -141,3 +144,5 @@
#if KERNEL_VERSION(5, 9, 0) > LINUX_VERSION_CODE
#define HAVE_TSK_IN_GUP
#endif
+
+#endif /* KNI_COMPAT_H */
diff --git a/lib/kni/rte_kni_fifo.h b/lib/kni/rte_kni_fifo.h
index d2ec82fe87..2ff71554c0 100644
--- a/lib/kni/rte_kni_fifo.h
+++ b/lib/kni/rte_kni_fifo.h
@@ -2,7 +2,8 @@
* Copyright(c) 2010-2014 Intel Corporation
*/
-
+#ifndef RTE_KNI_FIFO_H
+#define RTE_KNI_FIFO_H
/**
* @internal when c11 memory model enabled use c11 atomic memory barrier.
@@ -115,3 +116,5 @@ kni_fifo_free_count(struct rte_kni_fifo *fifo)
uint32_t fifo_read = __KNI_LOAD_ACQUIRE(&fifo->read);
return (fifo_read - fifo_write - 1) & (fifo->len - 1);
}
+
+#endif /* RTE_KNI_FIFO_H */
--
2.25.1
next prev parent reply other threads:[~2022-02-09 3:03 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1644374873.git.liwg06@foxmail.com>
2022-02-09 3:02 ` [PATCH v2 01/16] bus/dpaa: " Weiguo Li
2022-02-09 3:02 ` [PATCH v2 02/16] event/octeontx: " Weiguo Li
2022-02-09 3:02 ` [PATCH v2 03/16] net/cxgbe: " Weiguo Li
2022-02-09 3:02 ` [PATCH v2 04/16] net/enetfec: " Weiguo Li
2022-02-09 3:02 ` [PATCH v2 05/16] net/i40e: " Weiguo Li
2022-02-09 3:02 ` [PATCH v2 06/16] net/netvsc: " Weiguo Li
2022-02-09 6:28 ` Stephen Hemminger
2022-02-09 9:25 ` Bruce Richardson
2022-02-09 3:02 ` [PATCH v2 07/16] net/qede: " Weiguo Li
2022-02-09 3:02 ` [PATCH v2 08/16] net/tap: " Weiguo Li
2022-02-09 6:28 ` Stephen Hemminger
2022-02-09 3:02 ` [PATCH v2 09/16] net/virtio: " Weiguo Li
2022-02-09 3:02 ` [PATCH v2 10/16] raw/ifpga/base: " Weiguo Li
2022-02-09 3:02 ` Weiguo Li [this message]
2022-02-09 3:02 ` [PATCH v2 12/16] acl: " Weiguo Li
2022-02-09 9:42 ` Ananyev, Konstantin
2022-02-09 10:12 ` Weiguo Li
2022-02-09 3:16 ` [PATCH v2 13/16] eal: " Weiguo Li
2022-02-09 3:16 ` [PATCH v2 14/16] efd: " Weiguo Li
2022-02-09 3:16 ` [PATCH v2 15/16] hash: " Weiguo Li
2022-02-09 3:16 ` [PATCH v2 16/16] pcapng: " Weiguo Li
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=tencent_F64448E9987C8F8DD08B44C47CF22C9E320A@qq.com \
--to=liwg06@foxmail.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).