From: patchwork-bot+netdevbpf@kernel.org
To: Harini Katakam <harini.katakam@amd.com>
Cc: nicolas.ferre@microchip.com, davem@davemloft.net,
richardcochran@gmail.com, claudiu.beznea@microchip.com,
andrei.pistirica@microchip.com, kuba@kernel.org,
edumazet@google.com, pabeni@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, michal.simek@amd.com,
harinikatakamlinux@gmail.com
Subject: Re: [PATCH net-next v5 0/3] Macb PTP minor updates
Date: Fri, 14 Apr 2023 05:20:20 +0000 [thread overview]
Message-ID: <168144962050.25322.10654838630358470877.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230411123712.11459-1-harini.katakam@amd.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 11 Apr 2023 18:07:09 +0530 you wrote:
> - Enable PTP unicast
> - Optimize HW timestamp reading
>
> v5:
> Remove unnecessary braces and !! in gem_has_ptp
>
> v4:
> Fix kernel test robot error; use static check for
> CONFIG_MACB_USE_HWTSTAMP where necessary
>
> [...]
Here is the summary with links:
- [net-next,v5,1/3] net: macb: Update gem PTP support check
https://git.kernel.org/netdev/net-next/c/adee474a3b43
- [net-next,v5,2/3] net: macb: Enable PTP unicast
https://git.kernel.org/netdev/net-next/c/ee4e92c26c60
- [net-next,v5,3/3] net: macb: Optimize reading HW timestamp
https://git.kernel.org/netdev/net-next/c/8c0d0fe04449
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:[~2023-04-14 5:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-11 12:37 [PATCH net-next v5 0/3] Macb PTP minor updates Harini Katakam
2023-04-11 12:37 ` [PATCH net-next v5 1/3] net: macb: Update gem PTP support check Harini Katakam
2023-04-11 12:37 ` [PATCH net-next v5 2/3] net: macb: Enable PTP unicast Harini Katakam
2023-04-11 12:37 ` [PATCH net-next v5 3/3] net: macb: Optimize reading HW timestamp Harini Katakam
2023-04-14 5:20 ` 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=168144962050.25322.10654838630358470877.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrei.pistirica@microchip.com \
--cc=claudiu.beznea@microchip.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=harini.katakam@amd.com \
--cc=harinikatakamlinux@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.simek@amd.com \
--cc=netdev@vger.kernel.org \
--cc=nicolas.ferre@microchip.com \
--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