From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Saeed Mahameed <saeedm@nvidia.com>,
Leon Romanovsky <leonro@nvidia.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
Chris Mi <cmi@nvidia.com>
Subject: Re: linux-next: Tree for Dec 9 (ethernet/mellanox/mlx5)
Date: Thu, 10 Dec 2020 09:20:00 +1100 [thread overview]
Message-ID: <20201210092000.4c28192c@canb.auug.org.au> (raw)
In-Reply-To: <e5519ac6-1d25-632a-9b55-087d8ffaf386@infradead.org>
[-- Attachment #1: Type: text/plain, Size: 894 bytes --]
Hi all,
On Wed, 9 Dec 2020 12:14:39 -0800 Randy Dunlap <rdunlap@infradead.org> wrote:
>
> On 12/9/20 2:44 AM, Stephen Rothwell wrote:
> > Hi all,
> >
> > Changes since 20201208:
> >
>
> on i386:
>
> I see this warning:/note: repeated 106 times on i386 build:
>
> from ../drivers/net/ethernet/mellanox/mlx5/core/alloc.c:34:
> ../include/vdso/bits.h:7:26: warning: left shift count >= width of type [-Wshift-count-overflow]
> #define BIT(nr) (UL(1) << (nr))
> ^
> ../include/linux/mlx5/mlx5_ifc.h:10716:46: note: in expansion of macro ‘BIT’
> MLX5_HCA_CAP_GENERAL_OBJECT_TYPES_SAMPLER = BIT(0x20),
> ^~~
Introduced by commit
2a2970891647 ("net/mlx5: Add sample offload hardware bits and structures")
now in the net-next tree.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-12-09 22:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-09 10:44 linux-next: Tree for Dec 9 Stephen Rothwell
2020-12-09 14:04 ` John Garry
2020-12-09 20:14 ` linux-next: Tree for Dec 9 (ethernet/mellanox/mlx5) Randy Dunlap
2020-12-09 22:20 ` Stephen Rothwell [this message]
2020-12-10 0:58 ` linux-next: Tree for Dec 9 (usb/cdns3) Randy Dunlap
2020-12-10 8:52 ` Peter Chen
2020-12-10 9:53 ` Pawel Laszczak
2020-12-10 11:24 ` Pawel Laszczak
2020-12-10 16:41 ` Pawel Laszczak
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=20201210092000.4c28192c@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=cmi@nvidia.com \
--cc=leonro@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=saeedm@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