From: patchwork-bot+netdevbpf@kernel.org
To: Boon Khai Ng <boon.khai.ng@altera.com>
Cc: netdev@vger.kernel.org, linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, bpf@vger.kernel.org,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, mcoquelin.stm32@gmail.com,
alexandre.torgue@foss.st.com, linux@armlinux.org.uk,
ast@kernel.org, daniel@iogearbox.net, hawk@kernel.org,
john.fastabend@gmail.com, 0x1207@gmail.com,
matthew.gerlach@altera.com, tien.sung.ang@altera.com,
mun.yew.tham@altera.com, rohan.g.thomas@altera.com
Subject: Re: [PATCH net-next v5 0/3] Refactoring designware VLAN code.
Date: Sat, 10 May 2025 00:40:31 +0000 [thread overview]
Message-ID: <174683763150.3852829.17036982288908409763.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250507063812.34000-1-boon.khai.ng@altera.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 7 May 2025 14:38:09 +0800 you wrote:
> Refactoring designware VLAN code and introducing support for
> hardware-accelerated VLAN stripping for dwxgmac2 IP,
> the current patch set consists of two key changes:
>
> 1) Refactoring VLAN Functions:
> The first change involves moving common VLAN-related functions
> of the DesignWare Ethernet MAC into a dedicated file, stmmac_vlan.c.
> This refactoring aims to improve code organization and maintainability
> by centralizing VLAN handling logic.
>
> [...]
Here is the summary with links:
- [net-next,v5,1/3] net: stmmac: Refactor VLAN implementation
https://git.kernel.org/netdev/net-next/c/1d2c7a5fee31
- [net-next,v5,2/3] net: stmmac: stmmac_vlan: rename VLAN functions and symbol to generic symbol.
https://git.kernel.org/netdev/net-next/c/f3acaf7364a6
- [net-next,v5,3/3] net: stmmac: dwxgmac2: Add support for HW-accelerated VLAN stripping
https://git.kernel.org/netdev/net-next/c/534df0c1724b
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:[~2025-05-10 0:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-07 6:38 [PATCH net-next v5 0/3] Refactoring designware VLAN code Boon Khai Ng
2025-05-07 6:38 ` [PATCH net-next v5 1/3] net: stmmac: Refactor VLAN implementation Boon Khai Ng
2025-05-07 6:38 ` [PATCH net-next v5 2/3] net: stmmac: stmmac_vlan: rename VLAN functions and symbol to generic symbol Boon Khai Ng
2025-05-07 6:38 ` [PATCH net-next v5 3/3] net: stmmac: dwxgmac2: Add support for HW-accelerated VLAN stripping Boon Khai Ng
2025-05-10 0: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=174683763150.3852829.17036982288908409763.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=0x1207@gmail.com \
--cc=alexandre.torgue@foss.st.com \
--cc=andrew+netdev@lunn.ch \
--cc=ast@kernel.org \
--cc=boon.khai.ng@altera.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hawk@kernel.org \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=linux@armlinux.org.uk \
--cc=matthew.gerlach@altera.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=mun.yew.tham@altera.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rohan.g.thomas@altera.com \
--cc=tien.sung.ang@altera.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.