From: levendsayar@gmail.com
To: thomas@monjalon.net
Cc: dev@dpdk.org, Levend Sayar <levendsayar@gmail.com>,
Harry van Haaren <harry.van.haaren@intel.com>
Subject: [dpdk-dev] [PATCH v3] service: support C++ linkage
Date: Thu, 9 Jul 2020 15:32:16 +0300 [thread overview]
Message-ID: <20200709123216.47707-1-levendsayar@gmail.com> (raw)
In-Reply-To: <20200707122516.28630-1-levendsayar@gmail.com>
From: Levend Sayar <levendsayar@gmail.com>
"extern C" define is added to rte_service_component.h file
to be able to use in C++ context
Signed-off-by: Levend Sayar <levendsayar@gmail.com>
Acked-by: Harry van Haaren <harry.van.haaren@intel.com>
---
lib/librte_eal/include/rte_service_component.h | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/lib/librte_eal/include/rte_service_component.h b/lib/librte_eal/include/rte_service_component.h
index b75aba11b..9e66ee7e2 100644
--- a/lib/librte_eal/include/rte_service_component.h
+++ b/lib/librte_eal/include/rte_service_component.h
@@ -9,6 +9,11 @@
* Include this file if you are writing a component that requires CPU cycles to
* operate, and you wish to run the component using service cores
*/
+
+#ifdef __cplusplus
+extern "C" {
+#endif
+
#include <rte_compat.h>
#include <rte_service.h>
@@ -130,4 +135,8 @@ int32_t rte_service_init(void);
*/
void rte_service_finalize(void);
+#ifdef __cplusplus
+}
+#endif
+
#endif /* _SERVICE_PRIVATE_H_ */
--
2.27.0
next prev parent reply other threads:[~2020-07-09 12:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-07 12:25 [dpdk-dev] [PATCH] build: C++ linkage support is added to rte_service_component.h file levendsayar
2020-07-07 14:19 ` Thomas Monjalon
2020-07-07 15:00 ` Van Haaren, Harry
2020-07-07 15:31 ` Levend Sayar
2020-07-09 12:32 ` levendsayar [this message]
2020-07-09 13:21 ` [dpdk-dev] [PATCH v3] service: support C++ linkage Thomas Monjalon
2020-07-09 13:56 ` Levend Sayar
2020-07-09 14:24 ` 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=20200709123216.47707-1-levendsayar@gmail.com \
--to=levendsayar@gmail.com \
--cc=dev@dpdk.org \
--cc=harry.van.haaren@intel.com \
--cc=thomas@monjalon.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.