From: patchwork-bot+netdevbpf@kernel.org
To: Horatiu Vultur <horatiu.vultur@microchip.com>
Cc: andrew@lunn.ch, hkallweit1@gmail.com, linux@armlinux.org.uk,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, richardcochran@gmail.com,
Parthiban.Veerasooran@microchip.com, kory.maincent@bootlin.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v7 0/2] net: phy: micrel: Add PTP support for lan8842
Date: Thu, 04 Sep 2025 00:50:09 +0000 [thread overview]
Message-ID: <175694700901.1251694.3717331290989416543.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250902121832.3258544-1-horatiu.vultur@microchip.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 2 Sep 2025 14:18:30 +0200 you wrote:
> The PTP block in lan8842 is the same as lan8814 so reuse all these
> functions. The first patch of the series just does cosmetic changes such
> that lan8842 can reuse the function lan8814_ptp_probe. There should not be
> any functional changes here. While the second patch adds the PTP support
> to lan8842.
>
> v6->v7:
> - the v6 was not sent by mistake to mailing lists, so this version just
> sends also to the mailing list
>
> [...]
Here is the summary with links:
- [net-next,v7,1/2] net: phy: micrel: Introduce function __lan8814_ptp_probe_once
https://git.kernel.org/netdev/net-next/c/b9e0c62057a8
- [net-next,v7,2/2] net: phy: micrel: Add PTP support for lan8842
https://git.kernel.org/netdev/net-next/c/13d8f54d92a9
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-09-04 0:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-02 12:18 Horatiu Vultur
2025-09-02 12:18 ` [PATCH net-next v7 1/2] net: phy: micrel: Introduce function __lan8814_ptp_probe_once Horatiu Vultur
2025-09-02 12:18 ` [PATCH net-next v7 2/2] net: phy: micrel: Add PTP support for lan8842 Horatiu Vultur
2025-09-04 0:50 ` 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=175694700901.1251694.3717331290989416543.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Parthiban.Veerasooran@microchip.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=horatiu.vultur@microchip.com \
--cc=kory.maincent@bootlin.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=richardcochran@gmail.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®