From: Thomas Monjalon <thomas@monjalon.net>
To: Weiguo Li <liwg06@foxmail.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH 02/16] event/octeontx: add define guards to avoid multi-inclusion
Date: Tue, 08 Feb 2022 17:27:05 +0100 [thread overview]
Message-ID: <22527224.6Emhk5qWAg@thomas> (raw)
In-Reply-To: <tencent_19CC77F2888048690C124FECA95A848B0E06@qq.com>
06/02/2022 04:58, Weiguo Li:
> Supplement define guards to prevent multiple inclusion.
>
> Signed-off-by: Weiguo Li <liwg06@foxmail.com>
> ---
> --- a/drivers/event/octeontx/timvf_worker.h
> +++ b/drivers/event/octeontx/timvf_worker.h
> +#ifndef __TIMVF_WORKER_H__
> +#define __TIMVF_WORKER_H__
Why these underscores?
It could be simply
#ifndef TIMVF_WORKER_H
next prev parent reply other threads:[~2022-02-08 16:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220206035846.2840462-1-liwg06@foxmail.com>
2022-02-06 3:58 ` [PATCH 02/16] event/octeontx: add define guards to avoid multi-inclusion Weiguo Li
2022-02-08 16:27 ` Thomas Monjalon [this message]
2022-02-09 3:02 ` [PATCH v2 00/16] " Weiguo Li
2022-02-09 6:29 ` Stephen Hemminger
2022-02-09 7:24 ` [PATCH v3 0/4] " Weiguo Li
2022-02-06 3:58 ` [PATCH 03/16] net/cxgbe: add define guards to avoid multiple inclusion Weiguo Li
2022-02-06 3:58 ` [PATCH 04/16] net/enetfec: " Weiguo Li
2022-02-06 3:58 ` [PATCH 05/16] net/i40e: " Weiguo Li
2022-02-06 3:58 ` [PATCH 06/16] net/netvsc: add define guards to avoid multi-inclusion Weiguo Li
2022-02-06 3:58 ` [PATCH 07/16] net/qede: " Weiguo Li
2022-02-06 3:58 ` [PATCH 08/16] net/tap: " Weiguo Li
2022-02-06 3:58 ` [PATCH 09/16] net/virtio: " Weiguo Li
2022-02-06 3:58 ` [PATCH 10/16] raw/ifpga/base: " Weiguo Li
2022-02-06 3:58 ` [PATCH 11/16] kni: " Weiguo Li
2022-02-06 3:58 ` [PATCH 12/16] acl: " Weiguo Li
2022-02-06 3:58 ` [PATCH 13/16] eal: " Weiguo Li
2022-02-06 16:24 ` Dmitry Kozlyuk
2022-02-06 3:58 ` [PATCH 14/16] efd: " Weiguo Li
2022-02-06 3:58 ` [PATCH 15/16] hash: " Weiguo Li
2022-02-06 3:58 ` [PATCH 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=22527224.6Emhk5qWAg@thomas \
--to=thomas@monjalon.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.