From: patchwork-bot+netdevbpf@kernel.org
To: Vladimir Oltean <vladimir.oltean@nxp.com>
Cc: netdev@vger.kernel.org, claudiu.manoil@nxp.com,
alexandre.belloni@bootlin.com, UNGLinuxDriver@microchip.com,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
shuah@kernel.org, richard.pearn@nxp.com,
xiaoliang.yang_1@nxp.com, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH net 0/4] Fix Felix DSA taprio gates after clock jump
Date: Tue, 29 Apr 2025 22:20:34 +0000 [thread overview]
Message-ID: <174596523475.1813341.4865840988683166459.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250426144859.3128352-1-vladimir.oltean@nxp.com>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Sat, 26 Apr 2025 17:48:54 +0300 you wrote:
> Richie Pearn presented a reproducible situation where traffic would get
> blocked on the NXP LS1028A switch if a certain taprio schedule was
> applied, and stepping the PTP clock would take place. The latter event
> is an expected initial occurrence, but also at runtime, for example when
> transitioning from one grandmaster to another.
>
> The issue is completely described in patch 1/4, which also contains
> the fix, but it has left me with some doubts regarding the need for
> vsc9959_tas_clock_adjust() in general.
>
> [...]
Here is the summary with links:
- [net,1/4] net: dsa: felix: fix broken taprio gate states after clock jump
https://git.kernel.org/netdev/net/c/426d487bca38
- [net,2/4] selftests: net: tsn_lib: create common helper for counting received packets
https://git.kernel.org/netdev/net/c/efa6eb7d77aa
- [net,3/4] selftests: net: tsn_lib: add window_size argument to isochron_do()
https://git.kernel.org/netdev/net/c/f52fe6efd61f
- [net,4/4] selftests: net: tc_taprio: new test
https://git.kernel.org/netdev/net/c/4eb9da050f00
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-29 22:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-26 14:48 [PATCH net 0/4] Fix Felix DSA taprio gates after clock jump Vladimir Oltean
2025-04-26 14:48 ` [PATCH net 1/4] net: dsa: felix: fix broken taprio gate states " Vladimir Oltean
2025-04-26 14:48 ` [PATCH net 2/4] selftests: net: tsn_lib: create common helper for counting received packets Vladimir Oltean
2025-04-26 14:48 ` [PATCH net 3/4] selftests: net: tsn_lib: add window_size argument to isochron_do() Vladimir Oltean
2025-04-26 14:48 ` [PATCH net 4/4] selftests: net: tc_taprio: new test Vladimir Oltean
2025-04-29 22: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=174596523475.1813341.4865840988683166459.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=UNGLinuxDriver@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=andrew+netdev@lunn.ch \
--cc=claudiu.manoil@nxp.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=richard.pearn@nxp.com \
--cc=shuah@kernel.org \
--cc=vladimir.oltean@nxp.com \
--cc=xiaoliang.yang_1@nxp.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