From: patchwork-bot+netdevbpf@kernel.org
To: Horatiu Vultur <horatiu.vultur@microchip.com>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
lars.povlsen@microchip.com, Steen.Hegelund@microchip.com,
daniel.machon@microchip.com, UNGLinuxDriver@microchip.com
Subject: Re: [PATCH net-next] net: microchip: vcap: Add tc flower keys for lan966x
Date: Fri, 10 Feb 2023 08:50:19 +0000 [thread overview]
Message-ID: <167601901931.32230.10675972834777188254.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230208130839.1696860-1-horatiu.vultur@microchip.com>
Hello:
This patch was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Wed, 8 Feb 2023 14:08:39 +0100 you wrote:
> Add the following TC flower filter keys to lan966x for IS2:
> - ipv4_addr (sip and dip)
> - ipv6_addr (sip and dip)
> - control (IPv4 fragments)
> - portnum (tcp and udp port numbers)
> - basic (L3 and L4 protocol)
> - vlan (outer vlan tag info)
> - tcp (tcp flags)
> - ip (tos field)
>
> [...]
Here is the summary with links:
- [net-next] net: microchip: vcap: Add tc flower keys for lan966x
https://git.kernel.org/netdev/net-next/c/47400aaea4ff
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:[~2023-02-10 8:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-08 13:08 [PATCH net-next] net: microchip: vcap: Add tc flower keys for lan966x Horatiu Vultur
2023-02-10 8:50 ` 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=167601901931.32230.10675972834777188254.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=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