From: patchwork-bot+netdevbpf@kernel.org
To: David Yang <mmyangfl@gmail.com>
Cc: netdev@vger.kernel.org, andrew@lunn.ch, olteanv@gmail.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, linux@armlinux.org.uk,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v6 0/5] net: dsa: yt921x: Add DCB/QoS support
Date: Tue, 03 Feb 2026 14:20:37 +0000 [thread overview]
Message-ID: <177012843762.1498169.4265155868013803304.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260131021854.3405036-1-mmyangfl@gmail.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Sat, 31 Jan 2026 10:18:46 +0800 you wrote:
> This series add DCB/QoS support to the driver.
>
> v5: https://lore.kernel.org/r/20260128215202.2244266-1-mmyangfl@gmail.com
> - fix xmit priority for tag driver
> v4: https://lore.kernel.org/r/20260127020847.1482724-1-mmyangfl@gmail.com
> - change the color for DEI bit and add a comment for it
> v3: https://lore.kernel.org/r/20260125001328.3784006-1-mmyangfl@gmail.com
> - fix port_del_dscp_prio()
> - split yt921x_chip_setup()
> v2: https://lore.kernel.org/r/20260122194233.2777550-1-mmyangfl@gmail.com
> - make DCB support optional
> - refine with enum yt921x_app_selector
> - add missing dscp_prio_mapping_is_global
> - fix pcp support
> v1: https://lore.kernel.org/r/20260119185935.2072685-1-mmyangfl@gmail.com
> - rebase
>
> [...]
Here is the summary with links:
- [net-next,v6,1/5] net: dsa: tag_yt921x: clarify priority and code fields
https://git.kernel.org/netdev/net-next/c/a63daf73a587
- [net-next,v6,2/5] net: dsa: tag_yt921x: add priority support
https://git.kernel.org/netdev/net-next/c/8cdb2cc9a11b
- [net-next,v6,3/5] net: dsa: yt921x: Refactor VLAN awareness setting
https://git.kernel.org/netdev/net-next/c/75b85703fd48
- [net-next,v6,4/5] net: dsa: yt921x: Refactor yt921x_chip_setup()
https://git.kernel.org/netdev/net-next/c/95e6bcab3c08
- [net-next,v6,5/5] net: dsa: yt921x: Add DCB/QoS support
https://git.kernel.org/netdev/net-next/c/d5f778353fd4
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-02-03 14:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-31 2:18 [PATCH net-next v6 0/5] net: dsa: yt921x: Add DCB/QoS support David Yang
2026-01-31 2:18 ` [PATCH net-next v6 1/5] net: dsa: tag_yt921x: clarify priority and code fields David Yang
2026-01-31 2:18 ` [PATCH net-next v6 2/5] net: dsa: tag_yt921x: add priority support David Yang
2026-01-31 2:18 ` [PATCH net-next v6 3/5] net: dsa: yt921x: Refactor VLAN awareness setting David Yang
2026-01-31 2:18 ` [PATCH net-next v6 4/5] net: dsa: yt921x: Refactor yt921x_chip_setup() David Yang
2026-01-31 2:18 ` [PATCH net-next v6 5/5] net: dsa: yt921x: Add DCB/QoS support David Yang
2026-02-02 13:10 ` Vladimir Oltean
2026-02-03 2:18 ` David Yang
2026-02-03 13:14 ` [PATCH net-next v6 0/5] " Vladimir Oltean
2026-02-03 14: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=177012843762.1498169.4265155868013803304.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mmyangfl@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