From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: Tyler Retzlaff <roretzla@linux.microsoft.com>, dev@dpdk.org
Cc: david.hunt@intel.com, mb@smartsharesystems.com
Subject: Re: [dpdk-dev] [PATCH v3] eal, power: use UINT64_MAX and UINT32_MAX
Date: Thu, 1 Apr 2021 12:22:48 +0100 [thread overview]
Message-ID: <eda88d53-d50d-e215-4181-758b74a6ff40@intel.com> (raw)
In-Reply-To: <1615853611-7253-1-git-send-email-roretzla@linux.microsoft.com>
On 16-Mar-21 12:13 AM, Tyler Retzlaff wrote:
> Use UINT64_MAX and UINT32_MAX instead of -1 or ~0 literal variations
> of different explicit widths when creating masks and sentinel values.
>
> some compilers generate a warning when applying a '-' to an unsigned
> literal so avoid this by initializing with unsigned preprocessor
> definitions where appropriate.
>
> Signed-off-by: Tyler Retzlaff <roretzla@linux.microsoft.com>
> ---
Acked-by: Anatoly Burakov <anatoly.burakov@intel.com>
--
Thanks,
Anatoly
next prev parent reply other threads:[~2021-04-01 11:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-09 23:44 [dpdk-dev] [PATCH] eal, power: don't use '-' sign with unsigned literals Tyler Retzlaff
2021-03-12 12:51 ` Burakov, Anatoly
2021-03-12 17:05 ` Tyler Retzlaff
2021-03-12 17:37 ` Bruce Richardson
2021-03-12 18:36 ` Tyler Retzlaff
2021-03-12 18:40 ` Tyler Retzlaff
2021-03-13 9:05 ` Morten Brørup
2021-03-15 15:36 ` [dpdk-dev] [PATCH v2] eal, power: use UINT64_MAX instead of -1ULL Tyler Retzlaff
2021-03-16 0:13 ` [dpdk-dev] [PATCH v3] eal, power: use UINT64_MAX and UINT32_MAX Tyler Retzlaff
2021-03-16 11:06 ` Morten Brørup
2021-04-01 11:22 ` Burakov, Anatoly [this message]
2021-04-19 9:43 ` Thomas Monjalon
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=eda88d53-d50d-e215-4181-758b74a6ff40@intel.com \
--to=anatoly.burakov@intel.com \
--cc=david.hunt@intel.com \
--cc=dev@dpdk.org \
--cc=mb@smartsharesystems.com \
--cc=roretzla@linux.microsoft.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).