From: Weiguo Li <liwg06@foxmail.com>
To: dev@dpdk.org
Cc: bruce.richardson@intel.com, talshn@nvidia.com
Subject: [PATCH v2 2/6] common/mlx5: fix the curly braces mismatch problem
Date: Mon, 7 Feb 2022 20:36:57 +0800 [thread overview]
Message-ID: <tencent_8D9150919A98269EF1D3CD081E1DA4EFE407@qq.com> (raw)
In-Reply-To: <20220207123701.3281556-1-liwg06@foxmail.com>
Remove the incomplete cplusplus guard in internal headers.
Fixes: 7525ebd8ebb0 ("common/mlx5: add glue functions on Windows")
Cc: talshn@nvidia.com
Signed-off-by: Weiguo Li <liwg06@foxmail.com>
---
drivers/common/mlx5/windows/mlx5_win_defs.h | 4 ----
drivers/common/mlx5/windows/mlx5_win_ext.h | 4 ----
2 files changed, 8 deletions(-)
diff --git a/drivers/common/mlx5/windows/mlx5_win_defs.h b/drivers/common/mlx5/windows/mlx5_win_defs.h
index 9f709ff30d..3554e4a7ff 100644
--- a/drivers/common/mlx5/windows/mlx5_win_defs.h
+++ b/drivers/common/mlx5/windows/mlx5_win_defs.h
@@ -5,10 +5,6 @@
#ifndef __MLX5_WIN_DEFS_H__
#define __MLX5_WIN_DEFS_H__
-#ifdef __cplusplus
-extern "C" {
-#endif
-
enum {
MLX5_CQE_OWNER_MASK = 1,
MLX5_CQE_REQ = 0,
diff --git a/drivers/common/mlx5/windows/mlx5_win_ext.h b/drivers/common/mlx5/windows/mlx5_win_ext.h
index b5d4484a13..6f69329a6f 100644
--- a/drivers/common/mlx5/windows/mlx5_win_ext.h
+++ b/drivers/common/mlx5/windows/mlx5_win_ext.h
@@ -5,10 +5,6 @@
#ifndef __MLX5_WIN_ETX_H__
#define __MLX5_WIN_ETX_H__
-#ifdef __cplusplus
-extern "C" {
-#endif
-
#include "mlx5_prm.h"
#include "mlx5devx.h"
--
2.25.1
next parent reply other threads:[~2022-02-07 12:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220207123701.3281556-1-liwg06@foxmail.com>
2022-02-07 12:36 ` Weiguo Li [this message]
2022-02-07 12:36 ` [PATCH v2 3/6] net/cxgbe: " Weiguo Li
2022-02-07 12:36 ` [PATCH v2 4/6] net/dpaa2: " Weiguo Li
2022-02-07 12:37 ` [PATCH v2 5/6] eal/windows: " Weiguo Li
2022-02-07 13:15 ` Dmitry Kozlyuk
2022-02-07 22:19 ` Kadam, Pallavi
2022-02-07 12:37 ` [PATCH v2 6/6] eventdev: remove cplusplus guard in private header file Weiguo Li
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_8D9150919A98269EF1D3CD081E1DA4EFE407@qq.com \
--to=liwg06@foxmail.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=talshn@nvidia.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).