From: Leon Romanovsky <leonro@nvidia.com>
To: Shannon Nelson <snelson@pensando.io>
Cc: <davem@davemloft.net>, <netdev@vger.kernel.org>,
<kuba@kernel.org>, <drivers@pensando.io>
Subject: Re: [PATCH net-next] ionic: no devlink_unregister if not registered
Date: Wed, 13 Oct 2021 03:33:49 +0300 [thread overview]
Message-ID: <YWYpbScU1qT6CagV@unreal> (raw)
In-Reply-To: <20211012231520.72582-1-snelson@pensando.io>
On Tue, Oct 12, 2021 at 04:15:20PM -0700, Shannon Nelson wrote:
> Don't try to unregister the devlink if it hasn't been registered
> yet. This bit of error cleanup code got missed in the recent
> devlink registration changes.
>
> Fixes: 7911c8bd546f ("ionic: Move devlink registration to be last devlink command")
> Cc: Leon Romanovsky <leonro@nvidia.com>
> Signed-off-by: Shannon Nelson <snelson@pensando.io>
> ---
> drivers/net/ethernet/pensando/ionic/ionic_devlink.c | 1 -
> 1 file changed, 1 deletion(-)
Thanks,
Reviewed-by: Leon Romanovsky <leonro@nvidia.com>
next prev parent reply other threads:[~2021-10-13 0:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-12 23:15 [PATCH net-next] ionic: no devlink_unregister if not registered Shannon Nelson
2021-10-13 0:33 ` Leon Romanovsky [this message]
2021-10-13 2:40 ` patchwork-bot+netdevbpf
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=YWYpbScU1qT6CagV@unreal \
--to=leonro@nvidia.com \
--cc=davem@davemloft.net \
--cc=drivers@pensando.io \
--cc=kuba@kernel.org \
--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).