From: Brian Dooley <brian.dooley@intel.com>
To: dev@dpdk.org
Cc: Brian Dooley <brian.dooley@intel.com>,
stable@dpdk.org, Bruce Richardson <bruce.richardson@intel.com>,
Ferruh Yigit <ferruh.yigit@intel.com>
Subject: [PATCH v2 08/11] kni: fix missing C++ guards
Date: Wed, 16 Feb 2022 15:14:53 +0000 [thread overview]
Message-ID: <20220216151456.114242-9-brian.dooley@intel.com> (raw)
In-Reply-To: <20220216151456.114242-1-brian.dooley@intel.com>
Some public header files were missing 'extern "C"' C++ guards,
and couldn't be used by C++ applications. Add the missing guards.
Fixes: 3fc5ca2f6352 ("kni: initial import")
Cc: stable@dpdk.org
Signed-off-by: Brian Dooley <brian.dooley@intel.com>
Acked-by: Bruce Richardson <bruce.richardson@intel.com>
---
v2: Added missing apostrophe to commit message.
---
lib/kni/rte_kni_common.h | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/lib/kni/rte_kni_common.h b/lib/kni/rte_kni_common.h
index b547ea5501..8d3ee0fa4f 100644
--- a/lib/kni/rte_kni_common.h
+++ b/lib/kni/rte_kni_common.h
@@ -6,6 +6,10 @@
#ifndef _RTE_KNI_COMMON_H_
#define _RTE_KNI_COMMON_H_
+#ifdef __cplusplus
+extern "C" {
+#endif
+
#ifdef __KERNEL__
#include <linux/if.h>
#include <asm/barrier.h>
@@ -136,4 +140,8 @@ struct rte_kni_device_info {
#define RTE_KNI_IOCTL_CREATE _IOWR(0, 2, struct rte_kni_device_info)
#define RTE_KNI_IOCTL_RELEASE _IOWR(0, 3, struct rte_kni_device_info)
+#ifdef __cplusplus
+}
+#endif
+
#endif /* _RTE_KNI_COMMON_H_ */
--
2.25.1
next prev parent reply other threads:[~2022-02-16 15:16 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-15 17:08 [PATCH 00/11] add " Brian Dooley
2022-02-15 17:08 ` [PATCH 01/11] eal: fix " Brian Dooley
2022-02-15 17:08 ` [PATCH 02/11] telemetry: " Brian Dooley
2022-02-15 17:08 ` [PATCH 03/11] ethdev: " Brian Dooley
2022-02-15 17:08 ` [PATCH 04/11] metrics: " Brian Dooley
2022-02-15 17:08 ` [PATCH 05/11] acl: " Brian Dooley
2022-02-15 17:08 ` [PATCH 06/11] compressdev: " Brian Dooley
2022-02-15 17:08 ` [PATCH 07/11] eventdev: " Brian Dooley
2022-02-15 17:08 ` [PATCH 08/11] kni: " Brian Dooley
2022-02-15 17:08 ` [PATCH 09/11] vhost: " Brian Dooley
2022-02-15 17:08 ` [PATCH 10/11] bpf: " Brian Dooley
2022-02-15 17:08 ` [PATCH 11/11] cryptodev: " Brian Dooley
2022-02-15 17:32 ` [PATCH 00/11] add " Bruce Richardson
2022-02-16 15:14 ` [PATCH v2 " Brian Dooley
2022-02-16 15:14 ` [PATCH v2 01/11] eal: fix " Brian Dooley
2022-02-16 15:14 ` [PATCH v2 02/11] telemetry: " Brian Dooley
2022-02-16 15:14 ` [PATCH v2 03/11] ethdev: " Brian Dooley
2022-02-16 15:14 ` [PATCH v2 04/11] metrics: " Brian Dooley
2022-02-16 15:14 ` [PATCH v2 05/11] acl: " Brian Dooley
2022-02-16 15:14 ` [PATCH v2 06/11] compressdev: " Brian Dooley
2022-02-16 15:14 ` [PATCH v2 07/11] eventdev: " Brian Dooley
2022-02-16 15:14 ` Brian Dooley [this message]
2022-02-16 15:14 ` [PATCH v2 09/11] vhost: " Brian Dooley
2022-02-17 7:50 ` Xia, Chenbo
2022-02-16 15:14 ` [PATCH v2 10/11] bpf: " Brian Dooley
2022-02-16 15:14 ` [PATCH v2 11/11] cryptodev: " Brian Dooley
2022-02-17 8:00 ` [PATCH 00/11] add " Tyler Retzlaff
2022-02-22 14:02 ` 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=20220216151456.114242-9-brian.dooley@intel.com \
--to=brian.dooley@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=stable@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).