From: patchwork-bot+netdevbpf@kernel.org
To: Russell King (Oracle) <linux@armlinux.org.uk>
Cc: andrew@lunn.ch, alexandre.torgue@foss.st.com,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, linux-arm-kernel@lists.infradead.org,
linux-stm32@st-md-mailman.stormreply.com, netdev@vger.kernel.org,
pabeni@redhat.com
Subject: Re: [PATCH net-next 0/2] net: stmmac: further ptp cleanups
Date: Tue, 10 Mar 2026 03:00:35 +0000 [thread overview]
Message-ID: <177311163503.2039470.12160246560923313829.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <aawDiK7DjcSXSs1X@shell.armlinux.org.uk>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Sat, 7 Mar 2026 10:52:56 +0000 you wrote:
> Hi,
>
> A couple of extra PTP cleanup patches.
>
> The first uses a local variable when setting n_ext_ts which is a minor
> simplification of the code. The second removes the now unnecessary
> "available" flag for the PPS outputs.
>
> [...]
Here is the summary with links:
- [net-next,1/2] net: stmmac: ptp: rearrange n_ext_ts initialisation
https://git.kernel.org/netdev/net-next/c/b560d4434f98
- [net-next,2/2] net: stmmac: ptp: remove redundant priv->pps[].available
https://git.kernel.org/netdev/net-next/c/687e7863f027
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:[~2026-03-10 3:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-07 10:52 [PATCH net-next 0/2] net: stmmac: further ptp cleanups Russell King (Oracle)
2026-03-07 10:53 ` [PATCH net-next 1/2] net: stmmac: ptp: rearrange n_ext_ts initialisation Russell King (Oracle)
2026-03-07 10:53 ` [PATCH net-next 2/2] net: stmmac: ptp: remove redundant priv->pps[].available Russell King (Oracle)
2026-03-10 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=177311163503.2039470.12160246560923313829.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexandre.torgue@foss.st.com \
--cc=andrew+netdev@lunn.ch \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=linux@armlinux.org.uk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.