From: patchwork-bot+netdevbpf@kernel.org
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
pabeni@redhat.com, andrew+netdev@lunn.ch, horms@kernel.org,
olteanv@gmail.com
Subject: Re: [PATCH net-next 0/2] net: dsa: mv88e6xxx: ethtool n-tuple follow ups
Date: Tue, 22 Sep 2026 11:40:08 +0000 [thread overview]
Message-ID: <179007720874.3575540.14084472427997041384.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260918185326.3940857-1-kuba@kernel.org>
Hello:
This series was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Fri, 18 Sep 2026 11:53:24 -0700 you wrote:
> Here are two small tweaks to the mv88e6xxx n-tuple filter handling
> suggested by Sashiko when reviewing commit b1fffc273112 ("net: dsa:
> mv88e6xxx: bound the policy rule dump by the caller's buffer size")
>
> At the high level the problem is that the driver has shared rule
> table but for some ops it doesn't check whether the rule operated
> on belongs to the port on which the ethtool request was sent.
>
> [...]
Here is the summary with links:
- [net-next,1/2] net: dsa: mv88e6xxx: check the port when reading back a policy rule
https://git.kernel.org/netdev/net-next/c/e3624f5eeac4
- [net-next,2/2] net: dsa: mv88e6xxx: check the port when deleting a policy rule
https://git.kernel.org/netdev/net-next/c/242ebf4c5114
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-09-22 11:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-18 18:53 [PATCH net-next 0/2] net: dsa: mv88e6xxx: ethtool n-tuple follow ups Jakub Kicinski
2026-09-18 18:53 ` [PATCH net-next 1/2] net: dsa: mv88e6xxx: check the port when reading back a policy rule Jakub Kicinski
2026-09-21 18:55 ` netdev-bot+sashiko
2026-09-18 18:53 ` [PATCH net-next 2/2] net: dsa: mv88e6xxx: check the port when deleting " Jakub Kicinski
2026-09-21 18:55 ` netdev-bot+sashiko
2026-09-22 11: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=179007720874.3575540.14084472427997041384.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--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