From: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>
To: Weiguo Li <liwg06@foxmail.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: RE: [PATCH v2 12/16] acl: add define guards to avoid multi-inclusion
Date: Wed, 9 Feb 2022 09:42:28 +0000 [thread overview]
Message-ID: <DM6PR11MB4491DA5012F667CE9C35C95B9A2E9@DM6PR11MB4491.namprd11.prod.outlook.com> (raw)
In-Reply-To: <tencent_95AD083B1D8AEFB41145918D181E9EF25307@qq.com>
> Supplement define guards to prevent multiple inclusion.
> It should noted that there is an exceptional case:
> lib/acl/acl_run_avx512_common.h is designed to be included
> several times.
>
> Signed-off-by: Weiguo Li <liwg06@foxmail.com>
> ---
> lib/acl/acl_run_altivec.h | 5 +++++
> lib/acl/acl_run_avx2.h | 5 +++++
> lib/acl/acl_run_avx512x16.h | 5 +++++
> lib/acl/acl_run_avx512x8.h | 5 +++++
> lib/acl/acl_run_neon.h | 5 +++++
> lib/acl/acl_run_sse.h | 5 +++++
> 6 files changed, 30 insertions(+)
Do we really need these changes?
All these headers are internal ones for acl_run_*.c and not
supposed to be included multiple times anyway.
next prev parent reply other threads:[~2022-02-09 9:42 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1644374873.git.liwg06@foxmail.com>
2022-02-09 3:02 ` [PATCH v2 01/16] bus/dpaa: " Weiguo Li
2022-02-09 3:02 ` [PATCH v2 02/16] event/octeontx: " Weiguo Li
2022-02-09 3:02 ` [PATCH v2 03/16] net/cxgbe: " Weiguo Li
2022-02-09 3:02 ` [PATCH v2 04/16] net/enetfec: " Weiguo Li
2022-02-09 3:02 ` [PATCH v2 05/16] net/i40e: " Weiguo Li
2022-02-09 3:02 ` [PATCH v2 06/16] net/netvsc: " Weiguo Li
2022-02-09 6:28 ` Stephen Hemminger
2022-02-09 9:25 ` Bruce Richardson
2022-02-09 3:02 ` [PATCH v2 07/16] net/qede: " Weiguo Li
2022-02-09 3:02 ` [PATCH v2 08/16] net/tap: " Weiguo Li
2022-02-09 6:28 ` Stephen Hemminger
2022-02-09 3:02 ` [PATCH v2 09/16] net/virtio: " Weiguo Li
2022-02-09 3:02 ` [PATCH v2 10/16] raw/ifpga/base: " Weiguo Li
2022-02-09 3:02 ` [PATCH v2 11/16] kni: " Weiguo Li
2022-02-09 3:02 ` [PATCH v2 12/16] acl: " Weiguo Li
2022-02-09 9:42 ` Ananyev, Konstantin [this message]
2022-02-09 10:12 ` Weiguo Li
2022-02-09 3:16 ` [PATCH v2 13/16] eal: " Weiguo Li
2022-02-09 3:16 ` [PATCH v2 14/16] efd: " Weiguo Li
2022-02-09 3:16 ` [PATCH v2 15/16] hash: " Weiguo Li
2022-02-09 3:16 ` [PATCH v2 16/16] pcapng: " 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=DM6PR11MB4491DA5012F667CE9C35C95B9A2E9@DM6PR11MB4491.namprd11.prod.outlook.com \
--to=konstantin.ananyev@intel.com \
--cc=dev@dpdk.org \
--cc=liwg06@foxmail.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).