From: patchwork-bot+netdevbpf@kernel.org
To: Luiz Angelo Daros de Luca <luizluca@gmail.com>
Cc: andrew@lunn.ch, olteanv@gmail.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
horms@kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, alsi@bang-olufsen.dk,
linusw@kernel.org
Subject: Re: [net-next PATCH 0/2] net: dsa: tag_rtl8_4: fixes doc and set keep
Date: Sun, 12 Apr 2026 16:20:23 +0000 [thread overview]
Message-ID: <177601082303.3330556.5967550202445648760.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260408-realtek_fixes-v1-0-915ff1404d56@gmail.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 08 Apr 2026 17:31:00 -0300 you wrote:
> This small series addresses two points in the rtl8_4 tagger used by the
> realtel rtl8365mb driver.
>
> The first patch updates the documentation of the tag format while the
> second patch sets the KEEP flag bit, ensuring that the switch
> respects the frame's VLAN format as provided by the kernel.
>
> [...]
Here is the summary with links:
- [net-next,1/2] net: dsa: tag_rtl8_4: update format description
https://git.kernel.org/netdev/net-next/c/297e1f411ed4
- [net-next,2/2] net: dsa: tag_rtl8_4: set KEEP flag
https://git.kernel.org/netdev/net-next/c/82f37bd9a4d7
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-04-12 16:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-08 20:31 [net-next PATCH 0/2] net: dsa: tag_rtl8_4: fixes doc and set keep Luiz Angelo Daros de Luca
2026-04-08 20:31 ` [net-next PATCH 1/2] net: dsa: tag_rtl8_4: update format description Luiz Angelo Daros de Luca
2026-04-08 20:31 ` [net-next PATCH 2/2] net: dsa: tag_rtl8_4: set KEEP flag Luiz Angelo Daros de Luca
2026-04-12 16:20 ` 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=177601082303.3330556.5967550202445648760.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alsi@bang-olufsen.dk \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luizluca@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox