From: patchwork-bot+netdevbpf@kernel.org
To: Daniel Machon <daniel.machon@microchip.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, lars.povlsen@microchip.com,
Steen.Hegelund@microchip.com, UNGLinuxDriver@microchip.com,
linux@armlinux.org.uk, netdev@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, horatiu.vultur@microchip.com,
rmk+kernel@armlinux.org.uk, u.kleine-koenig@pengutronix.de,
vladimir.oltean@nxp.com, yuehaibing@huawei.com
Subject: Re: [PATCH net-next v3 0/5] net: sparx5: add support for port mirroring
Date: Wed, 24 Apr 2024 12:10:29 +0000 [thread overview]
Message-ID: <171396062919.12224.8860329852076042768.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240420-port-mirroring-v3-0-0fe3ac52006d@microchip.com>
Hello:
This series was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:
On Sat, 20 Apr 2024 21:29:09 +0200 you wrote:
> This series adds support for port mirroring, and port mirroring stats,
> through tc matchall action FLOW_ACTION_MIRRED.
>
> The hardware has three independent mirroring probes. Each probe can be
> configured with a separate set of filtering conditions that must be
> fulfilled before traffic is mirrored.
>
> [...]
Here is the summary with links:
- [net-next,v3,1/5] net: sparx5: add new register definitions
https://git.kernel.org/netdev/net-next/c/8c82bfdd8499
- [net-next,v3,2/5] net: sparx5: add bookkeeping code for matchall rules
https://git.kernel.org/netdev/net-next/c/1ede4acf045c
- [net-next,v3,3/5] net: sparx5: add port mirroring implementation
https://git.kernel.org/netdev/net-next/c/4e50d72b3b95
- [net-next,v3,4/5] net: sparx5: add the tc glue to support port mirroring
https://git.kernel.org/netdev/net-next/c/2ac99ed9c3ef
- [net-next,v3,5/5] net: sparx5: add support for matchall mirror stats
https://git.kernel.org/netdev/net-next/c/5af946f4bb42
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:[~2024-04-24 12:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-20 19:29 [PATCH net-next v3 0/5] net: sparx5: add support for port mirroring Daniel Machon
2024-04-20 19:29 ` [PATCH net-next v3 1/5] net: sparx5: add new register definitions Daniel Machon
2024-04-20 19:29 ` [PATCH net-next v3 2/5] net: sparx5: add bookkeeping code for matchall rules Daniel Machon
2024-04-20 19:29 ` [PATCH net-next v3 3/5] net: sparx5: add port mirroring implementation Daniel Machon
2024-04-20 19:29 ` [PATCH net-next v3 4/5] net: sparx5: add the tc glue to support port mirroring Daniel Machon
2024-04-20 19:29 ` [PATCH net-next v3 5/5] net: sparx5: add support for matchall mirror stats Daniel Machon
2024-04-24 12:10 ` 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=171396062919.12224.8860329852076042768.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Steen.Hegelund@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=daniel.machon@microchip.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horatiu.vultur@microchip.com \
--cc=kuba@kernel.org \
--cc=lars.povlsen@microchip.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rmk+kernel@armlinux.org.uk \
--cc=u.kleine-koenig@pengutronix.de \
--cc=vladimir.oltean@nxp.com \
--cc=yuehaibing@huawei.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