From: David Marchand <david.marchand@6wind.com>
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCH 2/2] eal: move empty declarations to doc
Date: Fri, 13 Nov 2015 10:35:26 +0100 [thread overview]
Message-ID: <1447407326-13446-2-git-send-email-david.marchand@6wind.com> (raw)
In-Reply-To: <1447407326-13446-1-git-send-email-david.marchand@6wind.com>
No need for those forward declarations (which breaks build when asking for
C++11 or adding pedantic flag).
Signed-off-by: David Marchand <david.marchand@6wind.com>
---
lib/librte_eal/common/include/generic/rte_cpuflags.h | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/lib/librte_eal/common/include/generic/rte_cpuflags.h b/lib/librte_eal/common/include/generic/rte_cpuflags.h
index 61c4db1..5738a2a 100644
--- a/lib/librte_eal/common/include/generic/rte_cpuflags.h
+++ b/lib/librte_eal/common/include/generic/rte_cpuflags.h
@@ -47,12 +47,16 @@
/**
* Enumeration of all CPU features supported
*/
+#ifdef __DOXYGEN__
enum rte_cpu_flag_t;
+#endif
/**
* Enumeration of CPU registers
*/
+#ifdef __DOXYGEN__
enum cpu_register_t;
+#endif
typedef uint32_t cpuid_registers_t[4];
@@ -100,8 +104,10 @@ rte_cpu_get_features(uint32_t leaf, uint32_t subleaf, cpuid_registers_t out);
* 0 if flag is not available
* -ENOENT if flag is invalid
*/
+#ifdef __DOXYGEN__
static inline int
rte_cpu_get_flag_enabled(enum rte_cpu_flag_t feature);
+#endif
/**
* This function checks that the currently used CPU supports the CPU features
--
1.9.1
next prev parent reply other threads:[~2015-11-13 9:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-03 12:51 [dpdk-dev] [PATCH 1/2] lib: Fix pointer arithmetic for C++ Joongi Kim
2015-07-03 12:51 ` [dpdk-dev] [PATCH 2/2] eal: Fix compilation on C++ Joongi Kim
2015-08-17 15:29 ` Thomas Monjalon
2015-08-17 15:50 ` Thomas Monjalon
2015-11-13 9:35 ` [dpdk-dev] [PATCH 1/2] Revert "eal: fix C++ app build" David Marchand
2015-11-13 9:35 ` David Marchand [this message]
2015-11-23 15:19 ` [dpdk-dev] [PATCH 2/2] eal: move empty declarations to doc Thomas Monjalon
2015-08-17 15:22 ` [dpdk-dev] [PATCH 1/2] lib: Fix pointer arithmetic for C++ 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=1447407326-13446-2-git-send-email-david.marchand@6wind.com \
--to=david.marchand@6wind.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).