From: patchwork-bot+netdevbpf@kernel.org
To: Michael Chan <michael.chan@broadcom.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org, kuba@kernel.org,
gospo@broadcom.com, richardcochran@gmail.com,
pavan.chebbi@broadcom.com, edwin.peer@broadcom.com
Subject: Re: [PATCH net-next v2 0/7] bnxt_en: Add hardware PTP timestamping support on 575XX devices
Date: Mon, 28 Jun 2021 20:50:04 +0000 [thread overview]
Message-ID: <162491340447.24399.7662066111966364643.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1624814390-1300-1-git-send-email-michael.chan@broadcom.com>
Hello:
This series was applied to netdev/net-next.git (refs/heads/master):
On Sun, 27 Jun 2021 13:19:43 -0400 you wrote:
> Add PTP RX and TX hardware timestamp support on 575XX devices. These
> devices use the two-step method to implement the IEEE-1588 timestamping
> support.
>
> v2: Add spinlock to serialize access to the timecounter.
> Use .do_aux_work() for the periodic timer reading and to get the TX
> timestamp from the firmware.
> Propagate error code from ptp_clock_register().
> Make the 64-bit timer access safe on 32-bit CPUs.
> Read PHC using direct register access.
>
> [...]
Here is the summary with links:
- [net-next,v2,1/7] bnxt_en: Update firmware interface to 1.10.2.47
https://git.kernel.org/netdev/net-next/c/78eeadb8fea6
- [net-next,v2,2/7] bnxt_en: Get PTP hardware capability from firmware
https://git.kernel.org/netdev/net-next/c/ae5c42f0b92c
- [net-next,v2,3/7] bnxt_en: Add PTP clock APIs, ioctls, and ethtool methods
https://git.kernel.org/netdev/net-next/c/118612d519d8
- [net-next,v2,4/7] bnxt_en: Get the full 48-bit hardware timestamp periodically
https://git.kernel.org/netdev/net-next/c/390862f45c85
- [net-next,v2,5/7] bnxt_en: Get the RX packet timestamp
https://git.kernel.org/netdev/net-next/c/7f5515d19cd7
- [net-next,v2,6/7] bnxt_en: Transmit and retrieve packet timestamps
https://git.kernel.org/netdev/net-next/c/83bb623c968e
- [net-next,v2,7/7] bnxt_en: Enable hardware PTP support
https://git.kernel.org/netdev/net-next/c/93cb62d98e9c
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:[~2021-06-28 20:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-27 17:19 [PATCH net-next v2 0/7] bnxt_en: Add hardware PTP timestamping support on 575XX devices Michael Chan
2021-06-27 17:19 ` [PATCH net-next v2 1/7] bnxt_en: Update firmware interface to 1.10.2.47 Michael Chan
2021-06-27 17:19 ` [PATCH net-next v2 2/7] bnxt_en: Get PTP hardware capability from firmware Michael Chan
2021-06-27 17:19 ` [PATCH net-next v2 3/7] bnxt_en: Add PTP clock APIs, ioctls, and ethtool methods Michael Chan
2021-06-27 17:19 ` [PATCH net-next v2 4/7] bnxt_en: Get the full 48-bit hardware timestamp periodically Michael Chan
2021-06-27 17:19 ` [PATCH net-next v2 5/7] bnxt_en: Get the RX packet timestamp Michael Chan
2021-06-27 17:19 ` [PATCH net-next v2 6/7] bnxt_en: Transmit and retrieve packet timestamps Michael Chan
2021-06-27 17:19 ` [PATCH net-next v2 7/7] bnxt_en: Enable hardware PTP support Michael Chan
2021-06-28 20: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=162491340447.24399.7662066111966364643.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edwin.peer@broadcom.com \
--cc=gospo@broadcom.com \
--cc=kuba@kernel.org \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=pavan.chebbi@broadcom.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;
as well as URLs for NNTP newsgroup(s).