From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
Thomas Monjalon <thomas@monjalon.net>
Cc: <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2] ethdev: replace single bit masks with macros
Date: Fri, 22 Oct 2021 17:40:50 +0100 [thread overview]
Message-ID: <6e301fb7-b1f7-769d-cbc3-92502cd2a27b@intel.com> (raw)
In-Reply-To: <20211022073002.392299-1-andrew.rybchenko@oktetlabs.ru>
On 10/22/2021 8:30 AM, Andrew Rybchenko wrote:
> The macros RTE_BIT32 and RTE_BIT64 are used to replace single bit masks.
>
> Do not switch VLAN offload flags since type is not fixed size.
>
> Signed-off-by: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
Applied to dpdk-next-net/main, thanks.
prev parent reply other threads:[~2021-10-22 16:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-22 7:23 [dpdk-dev] [PATCH] " Andrew Rybchenko
2021-10-22 7:24 ` Thomas Monjalon
2021-10-22 7:30 ` [dpdk-dev] [PATCH v2] " Andrew Rybchenko
2021-10-22 16:40 ` Ferruh Yigit [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=6e301fb7-b1f7-769d-cbc3-92502cd2a27b@intel.com \
--to=ferruh.yigit@intel.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dev@dpdk.org \
--cc=thomas@monjalon.net \
/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).