From: patchwork-bot+netdevbpf@kernel.org
To: Vladimir Oltean <vladimir.oltean@nxp.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, andrew@lunn.ch,
claudiu.manoil@nxp.com, alexandre.belloni@bootlin.com,
horatiu.vultur@microchip.com, daniel.machon@microchip.com,
UNGLinuxDriver@microchip.com, xiaoliang.yang_1@nxp.com,
yangbo.lu@nxp.com, richardcochran@gmail.com
Subject: Re: [PATCH v2 net 0/5] Ocelot PTP fixes
Date: Sun, 08 Dec 2024 02:10:31 +0000 [thread overview]
Message-ID: <173362383100.3133782.13276065571353098430.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241205145519.1236778-1-vladimir.oltean@nxp.com>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 5 Dec 2024 16:55:14 +0200 you wrote:
> This is another attempt at "net: mscc: ocelot: be resilient to loss of
> PTP packets during transmission".
> https://lore.kernel.org/netdev/20241203164755.16115-1-vladimir.oltean@nxp.com/
>
> The central change is in patch 4/5. It recovers a port from a very
> reproducible condition where previously, it would become unable to take
> any hardware TX timestamp.
>
> [...]
Here is the summary with links:
- [v2,net,1/5] net: mscc: ocelot: fix memory leak on ocelot_port_add_txtstamp_skb()
https://git.kernel.org/netdev/net/c/4b01bec25bef
- [v2,net,2/5] net: mscc: ocelot: improve handling of TX timestamp for unknown skb
https://git.kernel.org/netdev/net/c/b6fba4b3f0be
- [v2,net,3/5] net: mscc: ocelot: ocelot->ts_id_lock and ocelot_port->tx_skbs.lock are IRQ-safe
https://git.kernel.org/netdev/net/c/0c53cdb95eb4
- [v2,net,4/5] net: mscc: ocelot: be resilient to loss of PTP packets during transmission
https://git.kernel.org/netdev/net/c/b454abfab525
- [v2,net,5/5] net: mscc: ocelot: perform error cleanup in ocelot_hwstamp_set()
https://git.kernel.org/netdev/net/c/43a4166349a2
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:[~2024-12-08 2:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-05 14:55 [PATCH v2 net 0/5] Ocelot PTP fixes Vladimir Oltean
2024-12-05 14:55 ` [PATCH v2 net 1/5] net: mscc: ocelot: fix memory leak on ocelot_port_add_txtstamp_skb() Vladimir Oltean
2024-12-05 14:55 ` [PATCH v2 net 2/5] net: mscc: ocelot: improve handling of TX timestamp for unknown skb Vladimir Oltean
2024-12-05 14:55 ` [PATCH v2 net 3/5] net: mscc: ocelot: ocelot->ts_id_lock and ocelot_port->tx_skbs.lock are IRQ-safe Vladimir Oltean
2024-12-05 14:55 ` [PATCH v2 net 4/5] net: mscc: ocelot: be resilient to loss of PTP packets during transmission Vladimir Oltean
2024-12-05 14:55 ` [PATCH v2 net 5/5] net: mscc: ocelot: perform error cleanup in ocelot_hwstamp_set() Vladimir Oltean
2024-12-08 2:06 ` [PATCH v2 net 0/5] Ocelot PTP fixes Jakub Kicinski
2024-12-08 2:10 ` 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=173362383100.3133782.13276065571353098430.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=UNGLinuxDriver@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=andrew@lunn.ch \
--cc=claudiu.manoil@nxp.com \
--cc=daniel.machon@microchip.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horatiu.vultur@microchip.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=richardcochran@gmail.com \
--cc=vladimir.oltean@nxp.com \
--cc=xiaoliang.yang_1@nxp.com \
--cc=yangbo.lu@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