From: patchwork-bot+netdevbpf@kernel•org
To: Guillaume Nault <gnault@redhat•com>
Cc: davem@davemloft•net, kuba@kernel•org, pabeni@redhat•com,
edumazet@google•com, netdev@vger•kernel.org, idosch@nvidia•com,
amcohen@nvidia•com, petrm@nvidia•com, razor@blackwall•org,
jbenc@redhat•com, leitao@debian•org, roopa@nvidia•com,
shemminger@vyatta•com
Subject: Re: [PATCH net 0/2] vxlan: Fix vxlan counters.
Date: Mon, 29 Apr 2024 12:40:28 +0000 [thread overview]
Message-ID: <171439442835.25762.12780825413327777805.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1714144439.git.gnault@redhat.com>
Hello:
This series was applied to netdev/net.git (main)
by David S. Miller <davem@davemloft•net>:
On Fri, 26 Apr 2024 17:27:15 +0200 you wrote:
> Like most virtual devices, vxlan needs special care when updating its
> netdevice counters. This is done in patch 1. Patch 2 just adds a
> missing VNI counter update (found while working on patch 1).
>
> Guillaume Nault (2):
> vxlan: Fix racy device stats updates.
> vxlan: Add missing VNI filter counter update in arp_reduce().
>
> [...]
Here is the summary with links:
- [net,1/2] vxlan: Fix racy device stats updates.
https://git.kernel.org/netdev/net/c/6dee402daba4
- [net,2/2] vxlan: Add missing VNI filter counter update in arp_reduce().
https://git.kernel.org/netdev/net/c/b22ea4ef4c34
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-04-29 12:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-26 15:27 [PATCH net 0/2] vxlan: Fix vxlan counters Guillaume Nault
2024-04-26 15:27 ` [PATCH net 1/2] vxlan: Fix racy device stats updates Guillaume Nault
2024-04-26 16:02 ` Eric Dumazet
2024-04-26 15:27 ` [PATCH net 2/2] vxlan: Add missing VNI filter counter update in arp_reduce() Guillaume Nault
2024-04-29 12:40 ` 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=171439442835.25762.12780825413327777805.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=amcohen@nvidia$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=gnault@redhat$(echo .)com \
--cc=idosch@nvidia$(echo .)com \
--cc=jbenc@redhat$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=leitao@debian$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=petrm@nvidia$(echo .)com \
--cc=razor@blackwall$(echo .)org \
--cc=roopa@nvidia$(echo .)com \
--cc=shemminger@vyatta$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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