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-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v6 0/2] net: dsa: yt921x: Add ACL support
Date: Wed, 10 Jun 2026 15:40:10 +0000 [thread overview]
Message-ID: <178110601014.3101197.15607035605580497941.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260606130011.307812-1-mmyangfl@gmail.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Sat, 6 Jun 2026 21:00:05 +0800 you wrote:
> v5: https://lore.kernel.org/r/20260602083755.79411-1-mmyangfl@gmail.com
> - validate tcp flags
> - fix TRAP action
> - unconditionally discard rule on deletion
> - trap traffic when hardware meters are exhausted
> - avoid devm_*
> v4: https://lore.kernel.org/r/20260528193726.1893365-1-mmyangfl@gmail.com
> - make use of software fallback
> - guard duplicate POLICE and PRIORITY
> v3: https://lore.kernel.org/r/20260523020704.503966-1-mmyangfl@gmail.com
> - handle ACL tag code
> - fix the upper bound for FLOW_DISSECTOR_KEY_PORTS_RANGE
> - extack messages when possible
> - check the redirect target for FLOW_ACTION_REDIRECT
> - fix candidates overrun
> - fix the activation order for rule and action
> v2: https://lore.kernel.org/r/20260520022242.120640-1-mmyangfl@gmail.com
> - v1 was mistakenly sent as v2
> v1: https://lore.kernel.org/r/20260514192140.3468543-1-mmyangfl@gmail.com
> - fix issue reported by test robot
>
> [...]
Here is the summary with links:
- [net-next,v6,1/2] net: dsa: tag_yt921x: handle ACL tag code
https://git.kernel.org/netdev/net-next/c/cf14ed49802e
- [net-next,v6,2/2] net: dsa: yt921x: Add ACL support
https://git.kernel.org/netdev/net-next/c/8eb9e7520b17
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-06-10 15:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-06 13:00 [PATCH net-next v6 0/2] net: dsa: yt921x: Add ACL support David Yang
2026-06-06 13:00 ` [PATCH net-next v6 1/2] net: dsa: tag_yt921x: handle ACL tag code David Yang
2026-06-06 13:00 ` [PATCH net-next v6 2/2] net: dsa: yt921x: Add ACL support David Yang
2026-06-10 15: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=178110601014.3101197.15607035605580497941.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=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