DPDK patches and discussions
 help / color / mirror / Atom feed
From: Weiguo Li <liwg06@foxmail.com>
To: dev@dpdk.org
Cc: pbhagavatula@marvell.com
Subject: [PATCH 6/6] eventdev: remove C++ include guard from private header
Date: Sun,  6 Feb 2022 08:44:14 +0800	[thread overview]
Message-ID: <tencent_E1C43CF0149F9645C4E9507D4F8C5488380A@qq.com> (raw)
In-Reply-To: <20220206004414.2801177-1-liwg06@foxmail.com>

The extern "C" declaration is useless in private header,
as previous patch (http://dpdk.org/patch/98948) noted.
This file contains only a half part of the include guard,
just remove it.

Fixes: d35e61322de52 ("eventdev: move inline APIs into separate structure")
Cc: pbhagavatula@marvell.com

Signed-off-by: Weiguo Li <liwg06@foxmail.com>
---
 lib/eventdev/eventdev_pmd.h | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/lib/eventdev/eventdev_pmd.h b/lib/eventdev/eventdev_pmd.h
index d0b0c00a60..b05ffce549 100644
--- a/lib/eventdev/eventdev_pmd.h
+++ b/lib/eventdev/eventdev_pmd.h
@@ -1366,8 +1366,4 @@ void
 event_dev_fp_ops_set(struct rte_event_fp_ops *fp_ops,
 		     const struct rte_eventdev *dev);
 
-#ifdef __cplusplus
-}
-#endif
-
 #endif /* _RTE_EVENTDEV_PMD_H_ */
-- 
2.25.1


      parent reply	other threads:[~2022-02-06  0:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20220206004414.2801177-1-liwg06@foxmail.com>
2022-02-06  0:44 ` [PATCH 1/6] bus/dpaa: fix the curly braces mismatch problem Weiguo Li
2022-02-07  9:26   ` Bruce Richardson
2022-02-06  0:44 ` [PATCH 2/6] common/mlx5: " Weiguo Li
2022-02-06  0:44 ` [PATCH 3/6] net/cxgbe: " Weiguo Li
2022-02-06  0:44 ` [PATCH 4/6] net/dpaa2: " Weiguo Li
2022-02-06  0:44 ` [PATCH 5/6] eal/windows: " Weiguo Li
2022-02-06 16:23   ` Dmitry Kozlyuk
2022-02-07 11:43   ` Weiguo Li
2022-02-06  0:44 ` Weiguo Li [this message]

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_E1C43CF0149F9645C4E9507D4F8C5488380A@qq.com \
    --to=liwg06@foxmail.com \
    --cc=dev@dpdk.org \
    --cc=pbhagavatula@marvell.com \
    /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).