All of lore.kernel.org
 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 0/2] net: bridge: fix vlan range dumps starting with a PVID
Date: Wed, 22 Jul 2026 18:10:18 +0000	[thread overview]
Message-ID: <178474381863.1967992.14565089382183026274.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260721140922.682265-1-razor@blackwall.org>

Hello:

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

On Tue, 21 Jul 2026 17:09:20 +0300 you wrote:
> Hi,
> Patch 01 fixes a bug that can skip dumping VLANs which a part of a range
> starting with a PVID VLAN and share the same flags. PVID VLAN should be
> always on its own. Patch 02 adds a selftest for this case. More information
> can be found in the respective patches.
> 
> Thanks,
>  Nik
> 
> [...]

Here is the summary with links:
  - [net,1/2] net: bridge: vlan: fix vlan range dumps starting with pvid
    https://git.kernel.org/netdev/net/c/43171c97e471
  - [net,2/2] selftests: net: bridge: test ranges with PVID VLAN
    https://git.kernel.org/netdev/net/c/679eb1e32d2c

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-07-22 18:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-21 14:09 [PATCH net 0/2] net: bridge: fix vlan range dumps starting with a PVID Nikolay Aleksandrov
2026-07-21 14:09 ` [PATCH net 1/2] net: bridge: vlan: fix vlan range dumps starting with pvid Nikolay Aleksandrov
2026-07-22 16:51   ` Ido Schimmel
2026-07-21 14:09 ` [PATCH net 2/2] selftests: net: bridge: test ranges with PVID VLAN Nikolay Aleksandrov
2026-07-22 16:52   ` Ido Schimmel
2026-07-22 18:10 ` 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=178474381863.1967992.14565089382183026274.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 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.