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, daniel@iogearbox.net,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
horms@kernel.org, dsahern@kernel.org
Subject: Re: [PATCH net-next 1/2] net: nlmon: Remove init and uninit functions
Date: Mon, 04 Mar 2024 10:20:44 +0000 [thread overview]
Message-ID: <170954764485.3200.9167784305864194205.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240301134215.1264416-1-leitao@debian.org>
Hello:
This series was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:
On Fri, 1 Mar 2024 05:42:13 -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: nlmon: Remove init and uninit functions
https://git.kernel.org/netdev/net-next/c/4f41ce81a919
- [net-next,2/2] net: nlmon: Simplify nlmon_get_stats64
https://git.kernel.org/netdev/net-next/c/26b5df99bf60
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-03-04 10:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-01 13:42 [PATCH net-next 1/2] net: nlmon: Remove init and uninit functions Breno Leitao
2024-03-01 13:42 ` [PATCH net-next 2/2] net: nlmon: Simplify nlmon_get_stats64 Breno Leitao
2024-03-01 14:09 ` Daniel Borkmann
2024-03-01 14:09 ` [PATCH net-next 1/2] net: nlmon: Remove init and uninit functions Daniel Borkmann
2024-03-04 10: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=170954764485.3200.9167784305864194205.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--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 \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.