From: Thomas Monjalon <thomas@monjalon.net>
To: dev@dpdk.org
Subject: Re: [PATCH 0/5] mlx5: remove useless constants
Date: Wed, 05 Nov 2025 22:37:49 +0100 [thread overview]
Message-ID: <2405113.teYOa0iCNi@thomas> (raw)
In-Reply-To: <20251102155617.4001783-1-thomas@monjalon.net>
02/11/2025 16:52, Thomas Monjalon:
> This is a cleanup of #define constants which are not used.
> Some unused constants are kept if they are part of a bitmap,
> or can serve as HW documentation.
>
> Thomas Monjalon (5):
> vdpa/mlx5: remove unused constant
> crypto/mlx5: remove unused constants
> regex/mlx5: remove useless constants
> common/mlx5: remove useless constants
> net/mlx5: remove useless constants
This last patch is split for constants and macros with parameters.
Applied
prev parent reply other threads:[~2025-11-05 21:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-02 15:52 Thomas Monjalon
2025-11-02 15:53 ` [PATCH 1/5] vdpa/mlx5: remove unused constant Thomas Monjalon
2025-11-02 15:53 ` [PATCH 2/5] crypto/mlx5: remove unused constants Thomas Monjalon
2025-11-02 15:53 ` [PATCH 3/5] regex/mlx5: remove useless constants Thomas Monjalon
2025-11-02 15:53 ` [PATCH 4/5] common/mlx5: " Thomas Monjalon
2025-11-02 15:53 ` [PATCH 5/5] net/mlx5: " Thomas Monjalon
2025-11-05 21:37 ` 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=2405113.teYOa0iCNi@thomas \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
/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).