From: Bruce Richardson <bruce.richardson@intel.com>
To: Praveen Shetty <praveen.shetty@intel.com>
Cc: <dev@dpdk.org>
Subject: Re: [PATCH v1] net/idpf: avoid truncation of constant value
Date: Wed, 9 Apr 2025 15:27:26 +0100 [thread overview]
Message-ID: <Z_aDznlc6Cd7nti4@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <20250409125440.7103-1-praveen.shetty@intel.com>
On Wed, Apr 09, 2025 at 12:54:40PM +0000, Praveen Shetty wrote:
> Truncation of constant value compiler warning was reported in clang/msvc
> compiler for the VIRTCHNL2_CAP_OEM bit setting.This is due to 64 bit number
> is initialized in a 32 bit enum.VIRTCHNL2_CAP_OEM capability is not used in
> the present dpdk code,so removing this bit setting from the dpdk to avoid
> the truncation.
Please just watch spacing after punctuation in commit message. Will fix on
apply as necessary, no need for new revision to fix it.
>
> Signed-off-by: Praveen Shetty <praveen.shetty@intel.com>
> ---
> drivers/net/intel/idpf/base/virtchnl2.h | 2 --
> 1 file changed, 2 deletions(-)
>
> diff --git a/drivers/net/intel/idpf/base/virtchnl2.h b/drivers/net/intel/idpf/base/virtchnl2.h
> index 3285a2b674..cf010c0504 100644
> --- a/drivers/net/intel/idpf/base/virtchnl2.h
> +++ b/drivers/net/intel/idpf/base/virtchnl2.h
> @@ -265,8 +265,6 @@ enum virtchnl2_cap_other {
> * if a reserved bit is set in a standard completion's tag.
> */
> VIRTCHNL2_CAP_MISS_COMPL_TAG = BIT_ULL(20),
> - /* This must be the last capability */
> - VIRTCHNL2_CAP_OEM = BIT_ULL(63),
> };
>
Although technically perhaps not as good as [1], this avoids significant
divergence from the shared base code, while still fixing the core issue.
Acked-by: Bruce Richardson <bruce.richardson@intel.com>
[1] https://patches.dpdk.org/project/dpdk/patch/1734537913-1159-1-git-send-email-andremue@linux.microsoft.com/
next prev parent reply other threads:[~2025-04-09 14:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-09 12:54 Praveen Shetty
2025-04-09 14:27 ` Bruce Richardson [this message]
2025-04-11 6:52 ` David Marchand
2025-04-11 13:51 ` Andre Muezerie
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=Z_aDznlc6Cd7nti4@bricha3-mobl1.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=praveen.shetty@intel.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).