patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Tal Shnaiderman <talshn@nvidia.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	Raslan Darawsheh <rasland@nvidia.com>,
	Ophir Munk <ophirmu@nvidia.com>,
	"stable@dpdk.org" <stable@dpdk.org>,
	Matan Azrad <matan@nvidia.com>
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH v2] mlx5: fix __mlx5_bit_off macro warning for Windows
Date: Tue, 12 Jan 2021 22:45:53 +0100	[thread overview]
Message-ID: <3301193.NFa3CnqSlU@thomas> (raw)
In-Reply-To: <MW2PR12MB2492E97E8CC8FFD6E68B4EDDDFAF0@MW2PR12MB2492.namprd12.prod.outlook.com>

07/01/2021 13:59, Matan Azrad:
> From: Tal Shnaiderman
> > While compiling with clang 11 the callers of the __mlx5_bit_off macro warns
> > on the cast of pointers to unsigned long which is a smaller int type in Windows.
> > 
> > warning: cast to smaller integer type 'unsigned long'
> > from 'u8 (*)[16]' [-Wpointer-to-int-cast]
> > 
> > To resolve it the type is changed to uintptr_t to be compatible for both Linux
> > and Windows.
> > 
> > Fixes: 865a0c15672c ("net/mlx5: add Direct Verbs prepare function")
> > Cc: stable@dpdk.org
> > 
> > Signed-off-by: Tal Shnaiderman <talshn@nvidia.com>
> Acked-by: Matan Azrad <matan@nvidia.com>

Applied to next-net-mlx, thanks.




      reply	other threads:[~2021-01-12 21:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-06 13:42 [dpdk-stable] [PATCH] " Tal Shnaiderman
2021-01-06 14:22 ` [dpdk-stable] [dpdk-dev] " Dmitry Kozlyuk
2021-01-07 11:40   ` Tal Shnaiderman
2021-01-07 11:45 ` [dpdk-stable] [PATCH v2] " Tal Shnaiderman
2021-01-07 12:59   ` Matan Azrad
2021-01-12 21:45     ` 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=3301193.NFa3CnqSlU@thomas \
    --to=thomas@monjalon.net \
    --cc=dev@dpdk.org \
    --cc=matan@nvidia.com \
    --cc=ophirmu@nvidia.com \
    --cc=rasland@nvidia.com \
    --cc=stable@dpdk.org \
    --cc=talshn@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).