From: patchwork-bot+netdevbpf@kernel.org
To: Ido Schimmel <idosch@nvidia.com>
Cc: netdev@vger.kernel.org, bridge@lists.linux.dev,
davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
edumazet@google.com, horms@kernel.org, razor@blackwall.org,
petrm@nvidia.com
Subject: Re: [PATCH net-next v3 0/2] bridge: mcast: Fix a false positive lockdep splat
Date: Tue, 21 Jul 2026 10:40:10 +0000 [thread overview]
Message-ID: <178463041064.221494.2647422230949250489.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260708122820.1298718-1-idosch@nvidia.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Wed, 8 Jul 2026 15:28:18 +0300 you wrote:
> Patch #1 fixes false positive lockdep splat. See the commit message for
> more details.
>
> Patch #2 is small cleanup following the previous patch.
>
> Targeting at net-next since this is a false positive that is only
> visible with lockdep enabled and the change is not small / trivial.
>
> [...]
Here is the summary with links:
- [net-next,v3,1/2] bridge: mcast: Fix a false positive lockdep splat
https://git.kernel.org/netdev/net-next/c/4b0eb6fbc1fd
- [net-next,v3,2/2] bridge: mcast: Remove unnecessary argument from br_multicast_alloc_query()
https://git.kernel.org/netdev/net-next/c/dbda4c27bd77
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:[~2026-07-21 10:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-08 12:28 [PATCH net-next v3 0/2] bridge: mcast: Fix a false positive lockdep splat Ido Schimmel
2026-07-08 12:28 ` [PATCH net-next v3 1/2] " Ido Schimmel
2026-07-09 14:08 ` Ido Schimmel
2026-07-08 12:28 ` [PATCH net-next v3 2/2] bridge: mcast: Remove unnecessary argument from br_multicast_alloc_query() Ido Schimmel
2026-07-21 10: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=178463041064.221494.2647422230949250489.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=idosch@nvidia.com \
--cc=kuba@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