Netdev Archive on lore.kernel.org
help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Saeed Mahameed <saeed@kernel.org>
Cc: davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org,
vladbu@nvidia.com, colin.king@canonical.com,
tim.gardner@canonical.com, naresh.kamboju@linaro.org,
linux-kernel@vger.kernel.org, saeedm@nvidia.com
Subject: Re: [net 1/7] net/mlx5: Bridge, fix uninitialized variable usage
Date: Wed, 08 Sep 2021 10:50:06 +0000 [thread overview]
Message-ID: <163109820689.21737.2273802109235024092.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210907212420.28529-2-saeed@kernel.org>
Hello:
This series was applied to netdev/net.git (refs/heads/master):
On Tue, 7 Sep 2021 14:24:14 -0700 you wrote:
> From: Vlad Buslov <vladbu@nvidia.com>
>
> In some conditions variable 'err' is not assigned with value in
> mlx5_esw_bridge_port_obj_attr_set() and mlx5_esw_bridge_port_changeupper()
> functions after recent changes to support LAG. Initialize the variable with
> zero value in both cases.
>
> [...]
Here is the summary with links:
- [net,1/7] net/mlx5: Bridge, fix uninitialized variable usage
https://git.kernel.org/netdev/net/c/8343268ec3cf
- [net,2/7] net/mlx5: Fix rdma aux device on devlink reload
https://git.kernel.org/netdev/net/c/897ae4b40e80
- [net,3/7] net/mlx5: Lag, don't update lag if lag isn't supported
https://git.kernel.org/netdev/net/c/da8252d5805d
- [net,4/7] net/mlx5: FWTrace, cancel work on alloc pd error flow
https://git.kernel.org/netdev/net/c/dfe6fd72b5f1
- [net,5/7] net/mlx5: Fix potential sleeping in atomic context
https://git.kernel.org/netdev/net/c/ee27e330a953
- [net,6/7] net/mlx5e: Fix mutual exclusion between CQE compression and HW TS
https://git.kernel.org/netdev/net/c/c91c1da72b47
- [net,7/7] net/mlx5e: Fix condition when retrieving PTP-rqn
https://git.kernel.org/netdev/net/c/8db6a54f3cae
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-09-08 10:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-07 21:24 [pull request][net 0/7] mlx5 fixes 2021-09-07 Saeed Mahameed
2021-09-07 21:24 ` [net 1/7] net/mlx5: Bridge, fix uninitialized variable usage Saeed Mahameed
2021-09-08 10:50 ` patchwork-bot+netdevbpf [this message]
2021-09-07 21:24 ` [net 2/7] net/mlx5: Fix rdma aux device on devlink reload Saeed Mahameed
2021-09-07 21:24 ` [net 3/7] net/mlx5: Lag, don't update lag if lag isn't supported Saeed Mahameed
2021-09-07 21:24 ` [net 4/7] net/mlx5: FWTrace, cancel work on alloc pd error flow Saeed Mahameed
2021-09-11 7:43 ` Pavel Machek
2021-09-07 21:24 ` [net 5/7] net/mlx5: Fix potential sleeping in atomic context Saeed Mahameed
2021-09-07 21:24 ` [net 6/7] net/mlx5e: Fix mutual exclusion between CQE compression and HW TS Saeed Mahameed
2021-09-07 21:24 ` [net 7/7] net/mlx5e: Fix condition when retrieving PTP-rqn Saeed Mahameed
2021-09-08 16:39 ` Jakub Kicinski
2021-09-08 17:34 ` 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=163109820689.21737.2273802109235024092.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=colin.king@canonical.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=naresh.kamboju@linaro.org \
--cc=netdev@vger.kernel.org \
--cc=saeed@kernel.org \
--cc=saeedm@nvidia.com \
--cc=tim.gardner@canonical.com \
--cc=vladbu@nvidia.com \
--subject='Re: [net 1/7] net/mlx5: Bridge, fix uninitialized variable usage' \
/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
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).