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,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
divya.koppera@microchip.com
Subject: Re: [PATCH net-next v3 0/2] net: phy: micrel: lan8814: Enable PTP_PF_PEROUT
Date: Tue, 09 Apr 2024 11:50:27 +0000 [thread overview]
Message-ID: <171266342776.5043.8472571400532563052.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240408064432.3881636-1-horatiu.vultur@microchip.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Mon, 8 Apr 2024 08:44:30 +0200 you wrote:
> Add support for PTP_PF_PEROUT to lan8814. First patch just enables
> the LTC at probe time, such that it is not required to enable
> timestamping to have the LTC enabled. While the second patch actually
> adds support for PTP_PF_PEROUT.
>
> v2->v3:
> - rebase on latest net-next
>
> [...]
Here is the summary with links:
- [net-next,v3,1/2] net: phy: micrel: lan8814: Enable LTC at probe time
https://git.kernel.org/netdev/net-next/c/9f6b3a498174
- [net-next,v3,2/2] net: phy: micrel: lan8814: Add support for PTP_PF_PEROUT
https://git.kernel.org/netdev/net-next/c/9e63941b8976
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-04-09 11:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-08 6:44 Horatiu Vultur
2024-04-08 6:44 ` [PATCH net-next v3 1/2] net: phy: micrel: lan8814: Enable LTC at probe time Horatiu Vultur
2024-04-08 6:44 ` [PATCH net-next v3 2/2] net: phy: micrel: lan8814: Add support for PTP_PF_PEROUT Horatiu Vultur
2024-04-09 11: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=171266342776.5043.8472571400532563052.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=divya.koppera@microchip.com \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=horatiu.vultur@microchip.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®