From: patchwork-bot+netdevbpf@kernel.org
To: Saeed Mahameed <saeed@kernel.org>
Cc: davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org,
saeedm@nvidia.com, elic@nvidia.com, leonro@nvidia.com
Subject: Re: [net-next 01/15] net/mlx5: Don't skip vport check
Date: Fri, 12 Mar 2021 00:30:14 +0000 [thread overview]
Message-ID: <161550901498.18262.17694065791280917601.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210311223723.361301-2-saeed@kernel.org>
Hello:
This series was applied to netdev/net-next.git (refs/heads/master):
On Thu, 11 Mar 2021 14:37:09 -0800 you wrote:
> From: Saeed Mahameed <saeedm@nvidia.com>
>
> Users of mlx5_eswitch_get_vport() are required to check return value
> prior to passing mlx5_vport further. Fix all the places to do not skip
> that check.
>
> Reviewed-by: Eli Cohen <elic@nvidia.com>
> Signed-off-by: Leon Romanovsky <leonro@nvidia.com>
> Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>
>
> [...]
Here is the summary with links:
- [net-next,01/15] net/mlx5: Don't skip vport check
https://git.kernel.org/netdev/net-next/c/7bef147a6ab6
- [net-next,02/15] net/mlx5: Remove impossible checks of interface state
https://git.kernel.org/netdev/net-next/c/d89edb360705
- [net-next,03/15] net/mlx5: Separate probe vs. reload flows
https://git.kernel.org/netdev/net-next/c/6dea2f7eff96
- [net-next,04/15] net/mlx5: Remove second FW tracer check
https://git.kernel.org/netdev/net-next/c/7e615b997802
- [net-next,05/15] net/mlx5: Don't rely on interface state bit
https://git.kernel.org/netdev/net-next/c/7ad67a20f28f
- [net-next,06/15] net/mlx5: Check returned value from health recover sequence
https://git.kernel.org/netdev/net-next/c/fe06992b04a9
- [net-next,07/15] net/mlx5e: CT, Avoid false lock dependency warning
https://git.kernel.org/netdev/net-next/c/76e68d950a17
- [net-next,08/15] net/mlx5e: fix mlx5e_tc_tun_update_header_ipv6 dummy definition
https://git.kernel.org/netdev/net-next/c/87f77a679797
- [net-next,09/15] net/mlx5e: Add missing include
https://git.kernel.org/netdev/net-next/c/5632817b144f
- [net-next,10/15] net/mlx5: Fix indir stable stubs
https://git.kernel.org/netdev/net-next/c/fbeab6be054c
- [net-next,11/15] net/mlx5e: mlx5_tc_ct_init does not fail
https://git.kernel.org/netdev/net-next/c/51ada5a52379
- [net-next,12/15] net/mlx5: SF, Fix return type
https://git.kernel.org/netdev/net-next/c/3094552bcd72
- [net-next,13/15] net/mlx5e: rep: Improve reg_cX conditions
https://git.kernel.org/netdev/net-next/c/03e219c4cf84
- [net-next,14/15] net/mlx5: Avoid unnecessary operation
https://git.kernel.org/netdev/net-next/c/61e9508f1e5e
- [net-next,15/15] net/mlx5e: Alloc flow spec using kvzalloc instead of kzalloc
https://git.kernel.org/netdev/net-next/c/9f4d9283388d
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-03-12 0:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-11 22:37 [pull request][net-next 00/15] mlx5 updates 2021-03-11 Saeed Mahameed
2021-03-11 22:37 ` [net-next 01/15] net/mlx5: Don't skip vport check Saeed Mahameed
2021-03-12 0:30 ` patchwork-bot+netdevbpf [this message]
2021-03-11 22:37 ` [net-next 02/15] net/mlx5: Remove impossible checks of interface state Saeed Mahameed
2021-03-11 22:37 ` [net-next 03/15] net/mlx5: Separate probe vs. reload flows Saeed Mahameed
2021-03-11 22:37 ` [net-next 04/15] net/mlx5: Remove second FW tracer check Saeed Mahameed
2021-03-11 22:37 ` [net-next 05/15] net/mlx5: Don't rely on interface state bit Saeed Mahameed
2021-03-11 22:37 ` [net-next 06/15] net/mlx5: Check returned value from health recover sequence Saeed Mahameed
2021-03-11 22:37 ` [net-next 07/15] net/mlx5e: CT, Avoid false lock dependency warning Saeed Mahameed
2021-03-11 22:37 ` [net-next 08/15] net/mlx5e: fix mlx5e_tc_tun_update_header_ipv6 dummy definition Saeed Mahameed
2021-03-11 22:37 ` [net-next 09/15] net/mlx5e: Add missing include Saeed Mahameed
2021-03-11 22:37 ` [net-next 10/15] net/mlx5: Fix indir stable stubs Saeed Mahameed
2021-03-11 22:37 ` [net-next 11/15] net/mlx5e: mlx5_tc_ct_init does not fail Saeed Mahameed
2021-03-11 22:37 ` [net-next 12/15] net/mlx5: SF, Fix return type Saeed Mahameed
2021-03-11 22:37 ` [net-next 13/15] net/mlx5e: rep: Improve reg_cX conditions Saeed Mahameed
2021-03-11 22:37 ` [net-next 14/15] net/mlx5: Avoid unnecessary operation Saeed Mahameed
2021-03-11 22:37 ` [net-next 15/15] net/mlx5e: Alloc flow spec using kvzalloc instead of kzalloc 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=161550901498.18262.17694065791280917601.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=elic@nvidia.com \
--cc=kuba@kernel.org \
--cc=leonro@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=saeed@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.