From: patchwork-bot+netdevbpf@kernel.org
To: Michael Chan <michael.chan@broadcom.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, pavan.chebbi@broadcom.com,
andrew.gospodarek@broadcom.com, richardcochran@gmail.com,
horms@kernel.org, przemyslaw.kitszel@intel.com
Subject: Re: [PATCH net-next v2 00/10] bnxt_en: PTP updates for net-next
Date: Mon, 01 Jul 2024 10:30:37 +0000 [thread overview]
Message-ID: <171982983709.14870.6930247684372535647.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240628193006.225906-1-michael.chan@broadcom.com>
Hello:
This series was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:
On Fri, 28 Jun 2024 12:29:55 -0700 you wrote:
> The first 5 patches implement the PTP feature on the new BCM5760X
> chips. The main new hardware feature is the new TX timestamp
> completion which enables the driver to retrieve the TX timestamp
> in NAPI without deferring to the PTP worker.
>
> The last 5 patches increase the number of TX PTP packets in-flight
> from 1 to 4 on the older BCM5750X chips. On these older chips, we
> need to call firmware in the PTP worker to retrieve the timestamp.
> We use an arry to keep track of the in-flight TX PTP packets.
>
> [...]
Here is the summary with links:
- [net-next,v2,01/10] bnxt_en: Add new TX timestamp completion definitions
https://git.kernel.org/netdev/net-next/c/be6b7ca3c2ae
- [net-next,v2,02/10] bnxt_en: Add is_ts_pkt field to struct bnxt_sw_tx_bd
https://git.kernel.org/netdev/net-next/c/449da97512f3
- [net-next,v2,03/10] bnxt_en: Allow some TX packets to be unprocessed in NAPI
https://git.kernel.org/netdev/net-next/c/ba0155f1e9fc
- [net-next,v2,04/10] bnxt_en: Add TX timestamp completion logic
https://git.kernel.org/netdev/net-next/c/1d294b4f903f
- [net-next,v2,05/10] bnxt_en: Add BCM5760X specific PHC registers mapping
https://git.kernel.org/netdev/net-next/c/4d588d32b032
- [net-next,v2,06/10] bnxt_en: Refactor all PTP TX timestamp fields into a struct
https://git.kernel.org/netdev/net-next/c/92595a0c0223
- [net-next,v2,07/10] bnxt_en: Remove an impossible condition check for PTP TX pending SKB
https://git.kernel.org/netdev/net-next/c/573f2a4bfcd4
- [net-next,v2,08/10] bnxt_en: Let bnxt_stamp_tx_skb() return error code
https://git.kernel.org/netdev/net-next/c/9bf688d40d66
- [net-next,v2,09/10] bnxt_en: Increase the max total outstanding PTP TX packets to 4
https://git.kernel.org/netdev/net-next/c/8aa2a79e9b95
- [net-next,v2,10/10] bnxt_en: Remove atomic operations on ptp->tx_avail
https://git.kernel.org/netdev/net-next/c/060338390787
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-07-01 10:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-28 19:29 [PATCH net-next v2 00/10] bnxt_en: PTP updates for net-next Michael Chan
2024-06-28 19:29 ` [PATCH net-next v2 01/10] bnxt_en: Add new TX timestamp completion definitions Michael Chan
2024-06-28 19:29 ` [PATCH net-next v2 02/10] bnxt_en: Add is_ts_pkt field to struct bnxt_sw_tx_bd Michael Chan
2024-06-28 19:29 ` [PATCH net-next v2 03/10] bnxt_en: Allow some TX packets to be unprocessed in NAPI Michael Chan
2024-06-28 19:29 ` [PATCH net-next v2 04/10] bnxt_en: Add TX timestamp completion logic Michael Chan
2024-06-28 19:30 ` [PATCH net-next v2 05/10] bnxt_en: Add BCM5760X specific PHC registers mapping Michael Chan
2024-06-28 19:30 ` [PATCH net-next v2 06/10] bnxt_en: Refactor all PTP TX timestamp fields into a struct Michael Chan
2024-06-28 19:30 ` [PATCH net-next v2 07/10] bnxt_en: Remove an impossible condition check for PTP TX pending SKB Michael Chan
2024-06-28 19:30 ` [PATCH net-next v2 08/10] bnxt_en: Let bnxt_stamp_tx_skb() return error code Michael Chan
2024-06-28 19:30 ` [PATCH net-next v2 09/10] bnxt_en: Increase the max total outstanding PTP TX packets to 4 Michael Chan
2024-06-28 19:30 ` [PATCH net-next v2 10/10] bnxt_en: Remove atomic operations on ptp->tx_avail Michael Chan
2024-07-01 10:30 ` 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=171982983709.14870.6930247684372535647.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew.gospodarek@broadcom.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pavan.chebbi@broadcom.com \
--cc=przemyslaw.kitszel@intel.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 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.