Netdev List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Nikolay Aleksandrov <razor@blackwall.org>
Cc: netdev@vger.kernel.org, idosch@nvidia.com, davem@davemloft.net,
	edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
	horms@kernel.org, bridge@lists.linux.dev
Subject: Re: [PATCH net] net: bridge: vlan: fix inverted default vlan notification
Date: Tue, 18 Aug 2026 01:30:08 +0000	[thread overview]
Message-ID: <178701660839.1820167.12374828576561003816.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260814141640.64958-1-razor@blackwall.org>

Hello:

This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Fri, 14 Aug 2026 17:16:40 +0300 you wrote:
> A notification should be emitted only when the vlan delete was successful
> and not otherwise. The proper check is if br/nbp_vlan_delete returned 0.
> 
> Fixes: f545923b4a6b ("net: bridge: vlan: notify on vlan add/delete/change flags")
> Signed-off-by: Nikolay Aleksandrov <razor@blackwall.org>
> ---
> Found this issue while preparing some vlan code cleanups.
> 
> [...]

Here is the summary with links:
  - [net] net: bridge: vlan: fix inverted default vlan notification
    https://git.kernel.org/netdev/net/c/21040c7f9315

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-08-18  1:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-14 14:16 [PATCH net] net: bridge: vlan: fix inverted default vlan notification Nikolay Aleksandrov
2026-08-16 11:02 ` Ido Schimmel
2026-08-18  1:30 ` 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=178701660839.1820167.12374828576561003816.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=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