From: patchwork-bot+netdevbpf@kernel.org
To: Maxime Chevallier <maxime.chevallier@bootlin.com>
Cc: alexandre.torgue@foss.st.com, joabreu@synopsys.com,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, mcoquelin.stm32@gmail.com,
richardcochran@gmail.com, alexis.lothore@bootlin.com,
thomas.petazzoni@bootlin.com, netdev@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
daniel.machon@microchip.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v4 0/9] Support external snapshots on dwmac1000
Date: Thu, 14 Nov 2024 03:00:50 +0000 [thread overview]
Message-ID: <173155325074.1464897.8509953412141339085.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241112170658.2388529-1-maxime.chevallier@bootlin.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 12 Nov 2024 18:06:48 +0100 you wrote:
> Hi,
>
> This is v4 on the series to support external snapshots on dwmac1000.
>
> The main change since v3 is the move of the fifo flush wait in the
> ptp_clock_info enable() function within the mutex that protects the ptp
> registers. Thanks Jakub and Paolo for spotting this.
>
> [...]
Here is the summary with links:
- [net-next,v4,1/9] net: stmmac: Don't modify the global ptp ops directly
https://git.kernel.org/netdev/net-next/c/80dc1ff787a9
- [net-next,v4,2/9] net: stmmac: Use per-hw ptp clock ops
https://git.kernel.org/netdev/net-next/c/13e908800c0d
- [net-next,v4,3/9] net: stmmac: Only update the auto-discovered PTP clock features
https://git.kernel.org/netdev/net-next/c/0bfd0afc746c
- [net-next,v4,4/9] net: stmmac: Introduce dwmac1000 ptp_clock_info and operations
https://git.kernel.org/netdev/net-next/c/8e7620726beb
- [net-next,v4,5/9] net: stmmac: Introduce dwmac1000 timestamping operations
https://git.kernel.org/netdev/net-next/c/477c3e1f6363
- [net-next,v4,6/9] net: stmmac: Enable timestamping interrupt on dwmac1000
https://git.kernel.org/netdev/net-next/c/774f57d6562d
- [net-next,v4,7/9] net: stmmac: Don't include dwmac4 definitions in stmmac_ptp
https://git.kernel.org/netdev/net-next/c/85cebb7279e8
- [net-next,v4,8/9] net: stmmac: Configure only the relevant bits for timestamping setup
https://git.kernel.org/netdev/net-next/c/62935443214e
- [net-next,v4,9/9] net: stmmac: dwmac_socfpga: This platform has GMAC
https://git.kernel.org/netdev/net-next/c/b818268d9250
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-11-14 3:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-12 17:06 Maxime Chevallier
2024-11-12 17:06 ` [PATCH net-next v4 1/9] net: stmmac: Don't modify the global ptp ops directly Maxime Chevallier
2024-11-12 17:06 ` [PATCH net-next v4 2/9] net: stmmac: Use per-hw ptp clock ops Maxime Chevallier
2024-11-12 17:06 ` [PATCH net-next v4 3/9] net: stmmac: Only update the auto-discovered PTP clock features Maxime Chevallier
2024-11-12 17:06 ` [PATCH net-next v4 4/9] net: stmmac: Introduce dwmac1000 ptp_clock_info and operations Maxime Chevallier
2024-11-12 17:06 ` [PATCH net-next v4 5/9] net: stmmac: Introduce dwmac1000 timestamping operations Maxime Chevallier
2024-11-12 17:06 ` [PATCH net-next v4 6/9] net: stmmac: Enable timestamping interrupt on dwmac1000 Maxime Chevallier
2024-11-12 17:06 ` [PATCH net-next v4 7/9] net: stmmac: Don't include dwmac4 definitions in stmmac_ptp Maxime Chevallier
2024-11-12 17:06 ` [PATCH net-next v4 8/9] net: stmmac: Configure only the relevant bits for timestamping setup Maxime Chevallier
2024-11-12 17:06 ` [PATCH net-next v4 9/9] net: stmmac: dwmac_socfpga: This platform has GMAC Maxime Chevallier
2024-11-14 3:00 ` 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=173155325074.1464897.8509953412141339085.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexandre.torgue@foss.st.com \
--cc=alexis.lothore@bootlin.com \
--cc=andrew+netdev@lunn.ch \
--cc=daniel.machon@microchip.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=joabreu@synopsys.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=maxime.chevallier@bootlin.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=richardcochran@gmail.com \
--cc=thomas.petazzoni@bootlin.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
all inboxes | Powered by JetHome®