From: patchwork-bot+netdevbpf@kernel.org
To: Lorenzo Bianconi <lorenzo@kernel.org>
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, netdev@vger.kernel.org,
michal.kubiak@intel.com
Subject: Re: [PATCH net-next v2 0/2] Add L2 hw acceleration for airoha_eth driver
Date: Sat, 12 Apr 2025 03:20:48 +0000 [thread overview]
Message-ID: <174442804876.562152.332810337107180556.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250409-airoha-flowtable-l2b-v2-0-4a1e3935ea92@kernel.org>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 09 Apr 2025 11:47:13 +0200 you wrote:
> Introduce the capability to offload L2 traffic defining flower rules in
> the PSE/PPE engine available on EN7581 SoC.
> Since the hw always reports L2/L3/L4 flower rules, link all L2 rules
> sharing the same L2 info (with different L3/L4 info) in the L2 subflows
> list of a given L2 PPE entry.
>
>
> [...]
Here is the summary with links:
- [net-next,v2,1/2] net: airoha: Add l2_flows rhashtable
https://git.kernel.org/netdev/net-next/c/b4916f67902e
- [net-next,v2,2/2] net: airoha: Add L2 hw acceleration support
https://git.kernel.org/netdev/net-next/c/cd53f622611f
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:[~2025-04-12 3:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-09 9:47 [PATCH net-next v2 0/2] Add L2 hw acceleration for airoha_eth driver Lorenzo Bianconi
2025-04-09 9:47 ` [PATCH net-next v2 1/2] net: airoha: Add l2_flows rhashtable Lorenzo Bianconi
2025-04-09 9:47 ` [PATCH net-next v2 2/2] net: airoha: Add L2 hw acceleration support Lorenzo Bianconi
2025-04-09 11:58 ` [PATCH net-next v2 0/2] Add L2 hw acceleration for airoha_eth driver Michal Kubiak
2025-04-12 3:20 ` 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=174442804876.562152.332810337107180556.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=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=lorenzo@kernel.org \
--cc=michal.kubiak@intel.com \
--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