From: patchwork-bot+netdevbpf@kernel.org
To: Saeed Mahameed <saeed@kernel.org>
Cc: davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org,
tariqt@nvidia.com, ayal@nvidia.com, saeedm@nvidia.com
Subject: Re: [net 1/8] net/mlx5e: Fix incompatible casting
Date: Wed, 02 Jun 2021 20:30:04 +0000 [thread overview]
Message-ID: <162266580456.6825.5582815229746730103.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210602013723.1142650-2-saeed@kernel.org>
Hello:
This series was applied to netdev/net.git (refs/heads/master):
On Tue, 1 Jun 2021 18:37:16 -0700 you wrote:
> From: Aya Levin <ayal@nvidia.com>
>
> Device supports setting of a single fec mode at a time, enforce this
> by bitmap_weight == 1. Input from fec command is in u32, avoid cast to
> unsigned long and use bitmap_from_arr32 to populate bitmap safely.
>
> Fixes: 4bd9d5070b92 ("net/mlx5e: Enforce setting of a single FEC mode")
> Signed-off-by: Aya Levin <ayal@nvidia.com>
> Reviewed-by: Tariq Toukan <tariqt@nvidia.com>
> Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>
>
> [...]
Here is the summary with links:
- [net,1/8] net/mlx5e: Fix incompatible casting
https://git.kernel.org/netdev/net/c/d8ec92005f80
- [net,2/8] net/mlx5e: Disable TLS offload for uplink representor
https://git.kernel.org/netdev/net/c/b38742e41177
- [net,3/8] net/mlx5: Check firmware sync reset requested is set before trying to abort it
https://git.kernel.org/netdev/net/c/5940e64281c0
- [net,4/8] net/mlx5e: Check for needed capability for cvlan matching
https://git.kernel.org/netdev/net/c/afe93f71b5d3
- [net,5/8] net/mlx5e: Fix adding encap rules to slow path
https://git.kernel.org/netdev/net/c/2a2c84facd4a
- [net,6/8] net/mlx5e: Fix HW TS with CQE compression according to profile
https://git.kernel.org/netdev/net/c/256f79d13c1d
- [net,7/8] net/mlx5e: Fix conflict with HW TS and CQE compression
https://git.kernel.org/netdev/net/c/5349cbba754e
- [net,8/8] net/mlx5: DR, Create multi-destination flow table with level less than 64
https://git.kernel.org/netdev/net/c/216214c64a8c
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2021-06-02 20:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-02 1:37 [pull request][net 0/8] mlx5 fixes 2021-06-01 Saeed Mahameed
2021-06-02 1:37 ` [net 1/8] net/mlx5e: Fix incompatible casting Saeed Mahameed
2021-06-02 17:10 ` Jakub Kicinski
2021-06-02 20:30 ` patchwork-bot+netdevbpf [this message]
2021-06-03 21:02 ` David Laight
2021-06-02 1:37 ` [net 2/8] net/mlx5e: Disable TLS offload for uplink representor Saeed Mahameed
2021-06-02 1:37 ` [net 3/8] net/mlx5: Check firmware sync reset requested is set before trying to abort it Saeed Mahameed
2021-06-02 1:37 ` [net 4/8] net/mlx5e: Check for needed capability for cvlan matching Saeed Mahameed
2021-06-02 1:37 ` [net 5/8] net/mlx5e: Fix adding encap rules to slow path Saeed Mahameed
2021-06-02 1:37 ` [net 6/8] net/mlx5e: Fix HW TS with CQE compression according to profile Saeed Mahameed
2021-06-02 1:37 ` [net 7/8] net/mlx5e: Fix conflict with HW TS and CQE compression Saeed Mahameed
2021-06-02 1:37 ` [net 8/8] net/mlx5: DR, Create multi-destination flow table with level less than 64 Saeed Mahameed
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=162266580456.6825.5582815229746730103.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=ayal@nvidia.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=saeed@kernel.org \
--cc=saeedm@nvidia.com \
--cc=tariqt@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).