From: patchwork-bot+netdevbpf@kernel.org
To: Breno Leitao <leitao@debian.org>
Cc: kuba@kernel.org, davem@davemloft.net, pabeni@redhat.com,
edumazet@google.com, roopa@nvidia.com, razor@blackwall.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
horms@kernel.org, bridge@lists.linux.dev
Subject: Re: [PATCH net-next 1/2] net: bridge: Do not allocate stats in the driver
Date: Thu, 29 Feb 2024 04:20:29 +0000 [thread overview]
Message-ID: <170918042910.11535.3465744324810868254.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240227182338.2739884-1-leitao@debian.org>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 27 Feb 2024 10:23:36 -0800 you wrote:
> With commit 34d21de99cea9 ("net: Move {l,t,d}stats allocation to core and
> convert veth & vrf"), stats allocation could be done on net core
> instead of this driver.
>
> With this new approach, the driver doesn't have to bother with error
> handling (allocation failure checking, making sure free happens in the
> right spot, etc). This is core responsibility now.
>
> [...]
Here is the summary with links:
- [net-next,1/2] net: bridge: Do not allocate stats in the driver
https://git.kernel.org/netdev/net-next/c/d35150c79ffc
- [net-next,2/2] net: bridge: Exit if multicast_init_stats fails
https://git.kernel.org/netdev/net-next/c/82a48affb36f
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:[~2024-02-29 4:20 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
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 [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=170918042910.11535.3465744324810868254.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.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=razor@blackwall.org \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).