From: patchwork-bot+netdevbpf@kernel.org
To: Leon Romanovsky <leon@kernel.org>
Cc: davem@davemloft.net, kuba@kernel.org, snelson@pensando.io,
leonro@nvidia.com, drivers@pensando.io,
linux-kernel@vger.kernel.org, moshe@nvidia.com,
netdev@vger.kernel.org
Subject: Re: [PATCH net-next] ionic: cleanly release devlink instance
Date: Wed, 21 Jul 2021 21:50:04 +0000 [thread overview]
Message-ID: <162690420440.1414.7018903583171488691.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <956213a5c415c30e7e9f9c20bb50bc5b50ba4d18.1626870761.git.leonro@nvidia.com>
Hello:
This patch was applied to netdev/net-next.git (refs/heads/master):
On Wed, 21 Jul 2021 15:39:44 +0300 you wrote:
> From: Leon Romanovsky <leonro@nvidia.com>
>
> The failure to register devlink will leave the system with dangled
> devlink resource, which is not cleaned if devlink_port_register() fails.
>
> In order to remove access to ".registered" field of struct devlink_port,
> require both devlink_register and devlink_port_register to success and
> check it through device pointer.
>
> [...]
Here is the summary with links:
- [net-next] ionic: cleanly release devlink instance
https://git.kernel.org/netdev/net-next/c/c2255ff47768
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2021-07-21 21:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-21 12:39 [PATCH net-next] ionic: cleanly release devlink instance Leon Romanovsky
2021-07-21 15:55 ` Shannon Nelson
2021-07-21 21:50 ` patchwork-bot+netdevbpf [this message]
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=162690420440.1414.7018903583171488691.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=drivers@pensando.io \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=leonro@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=moshe@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=snelson@pensando.io \
/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).