From: Stephen Hemminger <stephen@networkplumber.org>
To: Yong Zhang <zhang.yong25@zte.com.cn>
Cc: thomas@monjalon.net, dev@dpdk.org, wang.yong19@zte.com.cn,
li.min10@zte.com.cn, ran.ming@zte.com.cn
Subject: Re: raw/gdtc: use standard macros to optimize code style
Date: Tue, 10 Dec 2024 12:37:28 -0800 [thread overview]
Message-ID: <20241210123728.5e33f467@hermes.local> (raw)
In-Reply-To: <20241210021219.773622-1-zhang.yong25@zte.com.cn>
On Tue, 10 Dec 2024 10:11:30 +0800
Yong Zhang <zhang.yong25@zte.com.cn> wrote:
> Use RTE_BIT to optimize non-standard macro definitions
>
> Signed-off-by: Yong Zhang <zhang.yong25@zte.com.cn>
> ---
Code will end up the same, but it is easier to read.
Acked-by: Stephen Hemminger <stephen@networkplumber.org>
prev parent reply other threads:[~2024-12-10 20:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-10 2:11 Yong Zhang
2024-12-10 20:37 ` Stephen Hemminger [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=20241210123728.5e33f467@hermes.local \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=li.min10@zte.com.cn \
--cc=ran.ming@zte.com.cn \
--cc=thomas@monjalon.net \
--cc=wang.yong19@zte.com.cn \
--cc=zhang.yong25@zte.com.cn \
/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).