From: Thomas Monjalon <thomas@monjalon.net>
To: Weiguo Li <liwg06@foxmail.com>
Cc: dev@dpdk.org, bruce.richardson@intel.com, shreyansh.jain@nxp.com
Subject: Re: [PATCH v2 1/6] bus/dpaa: fix the curly braces mismatch problem
Date: Tue, 08 Feb 2022 17:24:19 +0100 [thread overview]
Message-ID: <3337422.QJadu78ljV@thomas> (raw)
In-Reply-To: <tencent_426C785E4E2922F07558BE4346C445946309@qq.com>
07/02/2022 13:36, Weiguo Li:
> 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>
Series applied, thanks.
It seems there are more useless C++ include guard in drivers and examples.
prev parent reply other threads:[~2022-02-08 16:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-07 12:36 Weiguo Li
2022-02-08 16:24 ` Thomas Monjalon [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=3337422.QJadu78ljV@thomas \
--to=thomas@monjalon.net \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=liwg06@foxmail.com \
--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).