From: Weiguo Li <liwg06@foxmail.com>
To: dev@dpdk.org
Cc: bruce.richardson@intel.com, shreyansh.jain@nxp.com
Subject: [PATCH v2 1/6] bus/dpaa: fix the curly braces mismatch problem
Date: Mon, 7 Feb 2022 20:36:56 +0800 [thread overview]
Message-ID: <tencent_426C785E4E2922F07558BE4346C445946309@qq.com> (raw)
Supplement the missing half of braces for the extern "C" block,
or remove the incomplete guard in internal header.
Fixes: 6d6b4f49a155 ("bus/dpaa: add FMAN hardware operations")
Fixes: 919eeaccb2ba ("bus/dpaa: introduce NXP DPAA bus driver skeleton")
Cc: shreyansh.jain@nxp.com
Signed-off-by: Weiguo Li <liwg06@foxmail.com>
---
drivers/bus/dpaa/include/fsl_fman.h | 4 ----
drivers/bus/dpaa/rte_dpaa_bus.h | 4 ++++
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/bus/dpaa/include/fsl_fman.h b/drivers/bus/dpaa/include/fsl_fman.h
index acb344584f..20690f8329 100644
--- a/drivers/bus/dpaa/include/fsl_fman.h
+++ b/drivers/bus/dpaa/include/fsl_fman.h
@@ -9,10 +9,6 @@
#include <rte_compat.h>
-#ifdef __cplusplus
-extern "C" {
-#endif
-
/* Status field in FD is updated on Rx side by FMAN with following information.
* Refer to field description in FM BG.
*/
diff --git a/drivers/bus/dpaa/rte_dpaa_bus.h b/drivers/bus/dpaa/rte_dpaa_bus.h
index 31a5ea3fca..54bb1436fd 100644
--- a/drivers/bus/dpaa/rte_dpaa_bus.h
+++ b/drivers/bus/dpaa/rte_dpaa_bus.h
@@ -17,6 +17,10 @@
#include <fsl_bman.h>
#include <netcfg.h>
+#ifdef __cplusplus
+extern "C" {
+#endif
+
/* This sequence number field is used to store event entry index for
* driver specific usage. For parallel mode queues, invalid
* index will be set and for atomic mode queues, valid value
--
2.25.1
next reply other threads:[~2022-02-07 12:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-07 12:36 Weiguo Li [this message]
2022-02-08 16: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=tencent_426C785E4E2922F07558BE4346C445946309@qq.com \
--to=liwg06@foxmail.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=shreyansh.jain@nxp.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).