DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@6wind.com>
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCH] eal: fix C++ compilation issue after headers rework
Date: Fri,  7 Nov 2014 07:26:20 +0100	[thread overview]
Message-ID: <1415341580-28210-1-git-send-email-david.marchand@6wind.com> (raw)
In-Reply-To: <CAKBXKmBUgTBWvMnQEfE_nms7p9v32edwa2V2oVuwZrx+ZRhPrA@mail.gmail.com>

Following the big headers rework, all C++ stuff has moved to arch-specific
headers. The generic headers should not contain this so that this is done only
once.
There was a remaining #ifdef __cplusplus in "eal: split CPU cycle operation to
architecture specific" (fa4001c30ee9).

Reported-by: Keunhong Lee <dlrmsghd@gmail.com>
Signed-off-by: David Marchand <david.marchand@6wind.com>
---
 lib/librte_eal/common/include/generic/rte_cycles.h | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/lib/librte_eal/common/include/generic/rte_cycles.h b/lib/librte_eal/common/include/generic/rte_cycles.h
index c42b90b..7700f41 100644
--- a/lib/librte_eal/common/include/generic/rte_cycles.h
+++ b/lib/librte_eal/common/include/generic/rte_cycles.h
@@ -202,8 +202,4 @@ rte_delay_ms(unsigned ms)
 	rte_delay_us(ms * 1000);
 }
 
-#ifdef __cplusplus
-}
-#endif
-
 #endif /* _RTE_CYCLES_H_ */
-- 
2.1.1

  parent reply	other threads:[~2014-11-07  6:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-06 20:21 [dpdk-dev] Bugs in newest patches Keunhong Lee
2014-11-06 21:05 ` Thomas Monjalon
2014-11-07  1:26   ` Keunhong Lee
2014-11-07  6:14     ` David Marchand
2014-11-07  6:26 ` David Marchand [this message]
2014-11-07 11:21   ` [dpdk-dev] [PATCH] eal: fix C++ compilation issue after headers rework 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=1415341580-28210-1-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).