From: patchwork-bot+netdevbpf@kernel.org
To: Breno Leitao <leitao@debian.org>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, keescook@chromium.org, idosch@nvidia.com,
razor@blackwall.org, amcohen@nvidia.com, petrm@nvidia.com,
jbenc@redhat.com, b.galvani@gmail.com, gavinl@nvidia.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 1/2] vxlan: Do not alloc tstats manually
Date: Mon, 11 Mar 2024 23:20:31 +0000 [thread overview]
Message-ID: <171019923159.27198.11426721044166113476.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240311112437.3813987-1-leitao@debian.org>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 11 Mar 2024 04:24:30 -0700 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 in 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] vxlan: Do not alloc tstats manually
https://git.kernel.org/netdev/net-next/c/e28c5efc3139
- [net-next,2/2] vxlan: Remove generic .ndo_get_stats64
https://git.kernel.org/netdev/net-next/c/195f88c57737
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-11 23:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-11 11:24 [PATCH net-next 1/2] vxlan: Do not alloc tstats manually Breno Leitao
2024-03-11 11:24 ` [PATCH net-next 2/2] vxlan: Remove generic .ndo_get_stats64 Breno Leitao
2024-03-11 11:36 ` [EXTERNAL] " Subbaraya Sundeep Bhatta
2024-03-11 11:34 ` [EXTERNAL] [PATCH net-next 1/2] vxlan: Do not alloc tstats manually Subbaraya Sundeep Bhatta
2024-03-11 23: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=171019923159.27198.11426721044166113476.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=amcohen@nvidia.com \
--cc=b.galvani@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gavinl@nvidia.com \
--cc=idosch@nvidia.com \
--cc=jbenc@redhat.com \
--cc=keescook@chromium.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=petrm@nvidia.com \
--cc=razor@blackwall.org \
/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