From: Raslan Darawsheh <rasland@nvidia.com>
To: Andre Muezerie <andremue@linux.microsoft.com>,
Dariusz Sosnowski <dsosnowski@nvidia.com>,
Viacheslav Ovsiienko <viacheslavo@nvidia.com>,
Bing Zhao <bingz@nvidia.com>, Ori Kam <orika@nvidia.com>,
Suanming Mou <suanmingm@nvidia.com>,
Matan Azrad <matan@nvidia.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH] common/mlx5: avoid warning about operation mixing different enum types
Date: Wed, 4 Jun 2025 18:02:04 +0300 [thread overview]
Message-ID: <31279308-bbc2-4ea3-b47d-6643642acc84@nvidia.com> (raw)
In-Reply-To: <1748389285-26763-1-git-send-email-andremue@linux.microsoft.com>
Hi,
On 28/05/2025 2:41 AM, Andre Muezerie wrote:
> When compiling with MSVC, warnings like the one below pop up:
>
> ../drivers/common/mlx5/mlx5_devx_cmds.c(554): warning C5287: operands
> are different enum types
> '<unnamed-enum-MLX5_GET_HCA_CAP_OP_MOD_GENERAL_DEVICE>' and
> '<unnamed-enum-MLX5_HCA_CAP_OPMOD_GET_MAX>'; use an explicit cast
> to silence this warning
>
> The values in both enums indicate that this sort of mixed bit
> manipulation is intentional, so this patch just uses an explicit
> cast to avoid the warning.
>
> Signed-off-by: Andre Muezerie <andremue@linux.microsoft.com>
Patch applied to next-net-mlx,
Kindest regards
Raslan Darawsheh
prev parent reply other threads:[~2025-06-04 15:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-27 23:41 Andre Muezerie
2025-06-03 16:41 ` Dariusz Sosnowski
2025-06-04 7:42 ` Dariusz Sosnowski
2025-06-04 15:18 ` Andre Muezerie
2025-06-05 8:32 ` Dariusz Sosnowski
2025-06-04 15:02 ` Raslan Darawsheh [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=31279308-bbc2-4ea3-b47d-6643642acc84@nvidia.com \
--to=rasland@nvidia.com \
--cc=andremue@linux.microsoft.com \
--cc=bingz@nvidia.com \
--cc=dev@dpdk.org \
--cc=dsosnowski@nvidia.com \
--cc=matan@nvidia.com \
--cc=orika@nvidia.com \
--cc=suanmingm@nvidia.com \
--cc=viacheslavo@nvidia.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).