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, leonro@nvidia.com, saeedm@nvidia.com,
moshe@nvidia.com, parav@nvidia.com
Subject: Re: [net 1/8] net/mlx5: Fix error path for set HCA defaults
Date: Thu, 17 Jun 2021 18:40:05 +0000 [thread overview]
Message-ID: <162395520516.2276.71617321171522091.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210616224015.14393-2-saeed@kernel.org>
Hello:
This series was applied to netdev/net.git (refs/heads/master):
On Wed, 16 Jun 2021 15:40:08 -0700 you wrote:
> From: Leon Romanovsky <leonro@nvidia.com>
>
> In the case of the failure to execute mlx5_core_set_hca_defaults(),
> we used wrong goto label to execute error unwind flow.
>
> Fixes: 5bef709d76a2 ("net/mlx5: Enable host PF HCA after eswitch is initialized")
> Reviewed-by: Saeed Mahameed <saeedm@nvidia.com>
> Reviewed-by: Moshe Shemesh <moshe@nvidia.com>
> Signed-off-by: Leon Romanovsky <leonro@nvidia.com>
> Reviewed-by: Parav Pandit <parav@nvidia.com>
> Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>
>
> [...]
Here is the summary with links:
- [net,1/8] net/mlx5: Fix error path for set HCA defaults
https://git.kernel.org/netdev/net/c/94a4b8414d3e
- [net,2/8] net/mlx5: Check that driver was probed prior attaching the device
https://git.kernel.org/netdev/net/c/2058cc9c8041
- [net,3/8] net/mlx5: E-Switch, Read PF mac address
https://git.kernel.org/netdev/net/c/bbc8222dc49d
- [net,4/8] net/mlx5: E-Switch, Allow setting GUID for host PF vport
https://git.kernel.org/netdev/net/c/ca36fc4d77b3
- [net,5/8] net/mlx5: SF_DEV, remove SF device on invalid state
https://git.kernel.org/netdev/net/c/c7d6c19b3bde
- [net,6/8] net/mlx5: DR, Fix STEv1 incorrect L3 decapsulation padding
https://git.kernel.org/netdev/net/c/65fb7d109abe
- [net,7/8] net/mlx5e: Don't create devices during unload flow
https://git.kernel.org/netdev/net/c/a5ae8fc9058e
- [net,8/8] net/mlx5: Reset mkey index on creation
https://git.kernel.org/netdev/net/c/0232fc2ddcf4
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-17 18:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-16 22:40 [pull request][net 0/8] mlx5 fixes 2021-06-16 Saeed Mahameed
2021-06-16 22:40 ` [net 1/8] net/mlx5: Fix error path for set HCA defaults Saeed Mahameed
2021-06-17 18:40 ` patchwork-bot+netdevbpf [this message]
2021-06-16 22:40 ` [net 2/8] net/mlx5: Check that driver was probed prior attaching the device Saeed Mahameed
2021-06-16 22:40 ` [net 3/8] net/mlx5: E-Switch, Read PF mac address Saeed Mahameed
2021-06-16 22:40 ` [net 4/8] net/mlx5: E-Switch, Allow setting GUID for host PF vport Saeed Mahameed
2021-06-16 22:40 ` [net 5/8] net/mlx5: SF_DEV, remove SF device on invalid state Saeed Mahameed
2021-06-16 22:40 ` [net 6/8] net/mlx5: DR, Fix STEv1 incorrect L3 decapsulation padding Saeed Mahameed
2021-06-16 22:40 ` [net 7/8] net/mlx5e: Don't create devices during unload flow Saeed Mahameed
2021-06-16 22:40 ` [net 8/8] net/mlx5: Reset mkey index on creation 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=162395520516.2276.71617321171522091.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=leonro@nvidia.com \
--cc=moshe@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=parav@nvidia.com \
--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 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.