From: patchwork-bot+netdevbpf@kernel.org
To: Petr Machata <petrm@nvidia.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, netdev@vger.kernel.org, horms@kernel.org,
idosch@nvidia.com, amcohen@nvidia.com, vladimir.oltean@nxp.com,
aroulin@nvidia.com, mlxsw@nvidia.com
Subject: Re: [PATCH net-next v4 0/7] net: ndo_fdb_add/del: Have drivers report whether they notified
Date: Sat, 16 Nov 2024 02:00:32 +0000 [thread overview]
Message-ID: <173172243225.2797219.9826426655274919043.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1731589511.git.petrm@nvidia.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 14 Nov 2024 15:09:52 +0100 you wrote:
> Currently when FDB entries are added to or deleted from a VXLAN netdevice,
> the VXLAN driver emits one notification, including the VXLAN-specific
> attributes. The core however always sends a notification as well, a generic
> one. Thus two notifications are unnecessarily sent for these operations. A
> similar situation comes up with bridge driver, which also emits
> notifications on its own.
>
> [...]
Here is the summary with links:
- [net-next,v4,1/7] ndo_fdb_add: Add a parameter to report whether notification was sent
https://git.kernel.org/netdev/net-next/c/4b42fbc6bd8f
- [net-next,v4,2/7] ndo_fdb_del: Add a parameter to report whether notification was sent
https://git.kernel.org/netdev/net-next/c/42575ad5aab9
- [net-next,v4,3/7] selftests: net: lib: Move logging from forwarding/lib.sh here
https://git.kernel.org/netdev/net-next/c/b219bcfcc92e
- [net-next,v4,4/7] selftests: net: lib: Move tests_run from forwarding/lib.sh here
https://git.kernel.org/netdev/net-next/c/601d9d70a40a
- [net-next,v4,5/7] selftests: net: lib: Move checks from forwarding/lib.sh here
https://git.kernel.org/netdev/net-next/c/af76b4431818
- [net-next,v4,6/7] selftests: net: lib: Add kill_process
https://git.kernel.org/netdev/net-next/c/46f6569cf075
- [net-next,v4,7/7] selftests: net: fdb_notify: Add a test for FDB notifications
https://git.kernel.org/netdev/net-next/c/15880bec9bc3
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-11-16 2:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-14 14:09 [PATCH net-next v4 0/7] net: ndo_fdb_add/del: Have drivers report whether they notified Petr Machata
2024-11-14 14:09 ` [PATCH net-next v4 1/7] ndo_fdb_add: Add a parameter to report whether notification was sent Petr Machata
2024-11-14 14:09 ` [Intel-wired-lan] " Petr Machata
2024-11-14 14:09 ` [PATCH net-next v4 2/7] ndo_fdb_del: " Petr Machata
2024-11-14 14:09 ` [Intel-wired-lan] " Petr Machata
2024-11-14 14:09 ` [PATCH net-next v4 3/7] selftests: net: lib: Move logging from forwarding/lib.sh here Petr Machata
2024-11-14 14:09 ` [PATCH net-next v4 4/7] selftests: net: lib: Move tests_run " Petr Machata
2024-11-14 14:09 ` [PATCH net-next v4 5/7] selftests: net: lib: Move checks " Petr Machata
2024-11-14 14:09 ` [PATCH net-next v4 6/7] selftests: net: lib: Add kill_process Petr Machata
2024-11-14 14:09 ` [PATCH net-next v4 7/7] selftests: net: fdb_notify: Add a test for FDB notifications Petr Machata
2024-11-16 2:00 ` 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=173172243225.2797219.9826426655274919043.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=amcohen@nvidia.com \
--cc=aroulin@nvidia.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=mlxsw@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.com \
--cc=vladimir.oltean@nxp.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.