From: patchwork-bot+netdevbpf@kernel.org
To: Horatiu Vultur <horatiu.vultur@microchip.com>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
UNGLinuxDriver@microchip.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
linux@armlinux.org.uk
Subject: Re: [PATCH net-next 0/2] net: lan966x: Add police and mirror using tc-matchall
Date: Mon, 03 Oct 2022 12:00:18 +0000 [thread overview]
Message-ID: <166479841859.31360.550157837191959952.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220930083540.347686-1-horatiu.vultur@microchip.com>
Hello:
This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Fri, 30 Sep 2022 10:35:38 +0200 you wrote:
> Add tc-matchall classifier offload support both for ingress and egress.
> For this add support for the port police and port mirroring action support.
> Port police can happen only on ingress while port mirroring is supported
> both on ingress and egress
>
> Horatiu Vultur (2):
> net: lan966x: Add port police support using tc-matchall
> net: lan966x: Add port mirroring support using tc-matchall
>
> [...]
Here is the summary with links:
- [net-next,1/2] net: lan966x: Add port police support using tc-matchall
https://git.kernel.org/netdev/net-next/c/5390334b59a3
- [net-next,2/2] net: lan966x: Add port mirroring support using tc-matchall
https://git.kernel.org/netdev/net-next/c/b69e95397c3c
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:[~2022-10-03 12:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-30 8:35 [PATCH net-next 0/2] net: lan966x: Add police and mirror using tc-matchall Horatiu Vultur
2022-09-30 8:35 ` [PATCH net-next 1/2] net: lan966x: Add port police support " Horatiu Vultur
2022-09-30 8:35 ` [PATCH net-next 2/2] net: lan966x: Add port mirroring " Horatiu Vultur
2022-10-03 12:00 ` 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=166479841859.31360.550157837191959952.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=UNGLinuxDriver@microchip.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horatiu.vultur@microchip.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--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