[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <167033041690.5968.18443824551119031476.git-patchwork-notify@kernel.org>
Date: Tue, 06 Dec 2022 12:40:16 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Horatiu Vultur <horatiu.vultur@...rochip.com>
Cc: netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, davem@...emloft.net,
edumazet@...gle.com, kuba@...nel.org, pabeni@...hat.com,
Steen.Hegelund@...rochip.com, lars.povlsen@...rochip.com,
daniel.machon@...rochip.com, richardcochran@...il.com,
UNGLinuxDriver@...rochip.com, olteanv@...il.com
Subject: Re: [PATCH net-next v3 0/4] net: lan966x: Enable PTP on bridge interfaces
Hello:
This series was applied to netdev/net-next.git (master)
by Paolo Abeni <pabeni@...hat.com>:
On Sat, 3 Dec 2022 11:43:44 +0100 you wrote:
> Before it was not allowed to run ptp on ports that are part of a bridge
> because in case of transparent clock the HW will still forward the frames
> so there would be duplicate frames.
> Now that there is VCAP support, it is possible to add entries in the VCAP
> to trap frames to the CPU and the CPU will forward these frames.
> The first part of the patch series, extends the VCAP support to be able to
> modify and get the rule, while the last patch uses the VCAP to trap the ptp
> frames.
>
> [...]
Here is the summary with links:
- [net-next,v3,1/4] net: microchip: vcap: Add vcap_get_rule
https://git.kernel.org/netdev/net-next/c/610c32b2ce66
- [net-next,v3,2/4] net: microchip: vcap: Add vcap_mod_rule
https://git.kernel.org/netdev/net-next/c/2662b3f93d26
- [net-next,v3,3/4] net: microchip: vcap: Add vcap_rule_get_key_u32
https://git.kernel.org/netdev/net-next/c/6009b61f80e0
- [net-next,v3,4/4] net: lan966x: Add ptp trap rules
https://git.kernel.org/netdev/net-next/c/72df3489fb10
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists