From: Nikolay Aleksandrov <razor@blackwall.org>
To: Breno Leitao <leitao@debian.org>,
kuba@kernel.org, davem@davemloft.net, pabeni@redhat.com,
edumazet@google.com, Roopa Prabhu <roopa@nvidia.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
horms@kernel.org,
"open list:ETHERNET BRIDGE" <bridge@lists.linux.dev>
Subject: Re: [PATCH net-next 2/2] net: bridge: Exit if multicast_init_stats fails
Date: Tue, 27 Feb 2024 21:02:46 +0200 [thread overview]
Message-ID: <f8a78ffd-3504-4cad-bbcf-553186f228f0@blackwall.org> (raw)
In-Reply-To: <20240227182338.2739884-2-leitao@debian.org>
On 2/27/24 20:23, Breno Leitao wrote:
> If br_multicast_init_stats() fails, there is no need to set lockdep
> classes. Just return from the error path.
>
> Signed-off-by: Breno Leitao <leitao@debian.org>
> ---
> net/bridge/br_device.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/net/bridge/br_device.c b/net/bridge/br_device.c
> index 4f636f7b0555..c366ccc8b3db 100644
> --- a/net/bridge/br_device.c
> +++ b/net/bridge/br_device.c
> @@ -135,10 +135,11 @@ static int br_dev_init(struct net_device *dev)
> br_vlan_flush(br);
> br_mdb_hash_fini(br);
> br_fdb_hash_fini(br);
> + return err;
> }
>
> netdev_lockdep_set_classes(dev);
> - return err;
> + return 0;
> }
>
> static void br_dev_uninit(struct net_device *dev)
Please send them as separate patches next time. These are not related
and shouldn't be a part of a set.
Acked-by: Nikolay Aleksandrov <razor@blackwall.org>
next prev parent reply other threads:[~2024-02-27 19:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-27 18:23 [PATCH net-next 1/2] net: bridge: Do not allocate stats in the driver Breno Leitao
2024-02-27 18:23 ` [PATCH net-next 2/2] net: bridge: Exit if multicast_init_stats fails Breno Leitao
2024-02-27 19:02 ` Nikolay Aleksandrov [this message]
2024-02-27 19:02 ` [PATCH net-next 1/2] net: bridge: Do not allocate stats in the driver Nikolay Aleksandrov
2024-02-29 4:20 ` 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=f8a78ffd-3504-4cad-bbcf-553186f228f0@blackwall.org \
--to=razor@blackwall.org \
--cc=bridge@lists.linux.dev \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=leitao@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=roopa@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®