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, andrew+netdev@lunn.ch,
pavan.chebbi@broadcom.com, andrew.gospodarek@broadcom.com
Subject: Re: [PATCH net-next v2 0/6] bnxt_en: Updates for net-next
Date: Mon, 12 Jan 2026 20:57:43 +0000 [thread overview]
Message-ID: <176825146303.1092878.12676174704649444710.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260108183521.215610-1-michael.chan@broadcom.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 8 Jan 2026 10:35:15 -0800 you wrote:
> This patchset updates the driver with a FW interface update to support
> FEC stats histogram and NVRAM defragmentation. Patch #2 adds PTP
> cross timestamps [1]. Patch #3 adds FEC histogram stats. Patch #4 adds
> NVRAM defragmentation support that prevents FW update failure when NVRAM
> is fragmented. Patch #5 improves RSS distribution accuracy when certain
> number of rings is in use. The last patch adds ethtool
> .get_link_ext_state() support.
>
> [...]
Here is the summary with links:
- [net-next,v2,1/6] bnxt_en: Update FW interface to 1.10.3.151
https://git.kernel.org/netdev/net-next/c/fdb573d675e3
- [net-next,v2,2/6] bnxt_en: Add PTP .getcrosststamp() interface to get device/host times
https://git.kernel.org/netdev/net-next/c/c470195b989f
- [net-next,v2,3/6] bnxt_en: Add support for FEC bin histograms
https://git.kernel.org/netdev/net-next/c/e1c9c8928b5b
- [net-next,v2,4/6] bnxt_en: Defrag the NVRAM region when resizing UPDATE region fails
https://git.kernel.org/netdev/net-next/c/743e683596fa
- [net-next,v2,5/6] bnxt_en: Use a larger RSS indirection table on P5_PLUS chips
https://git.kernel.org/netdev/net-next/c/51b9d3f948b8
- [net-next,v2,6/6] bnxt_en: Implement ethtool_ops -> get_link_ext_state()
https://git.kernel.org/netdev/net-next/c/bc87b14594e3
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2026-01-12 21:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-08 18:35 [PATCH net-next v2 0/6] bnxt_en: Updates for net-next Michael Chan
2026-01-08 18:35 ` [PATCH net-next v2 1/6] bnxt_en: Update FW interface to 1.10.3.151 Michael Chan
2026-01-08 18:35 ` [PATCH net-next v2 2/6] bnxt_en: Add PTP .getcrosststamp() interface to get device/host times Michael Chan
2026-01-08 18:35 ` [PATCH net-next v2 3/6] bnxt_en: Add support for FEC bin histograms Michael Chan
2026-01-08 18:35 ` [PATCH net-next v2 4/6] bnxt_en: Defrag the NVRAM region when resizing UPDATE region fails Michael Chan
2026-01-08 18:35 ` [PATCH net-next v2 5/6] bnxt_en: Use a larger RSS indirection table on P5_PLUS chips Michael Chan
2026-01-08 18:35 ` [PATCH net-next v2 6/6] bnxt_en: Implement ethtool_ops -> get_link_ext_state() Michael Chan
2026-01-12 20:57 ` patchwork-bot+netdevbpf [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-05-01 0:30 [PATCH net-next v2 0/6] bnxt_en: Updates for net-next Michael Chan
2024-05-02 14:40 ` patchwork-bot+netdevbpf
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=176825146303.1092878.12676174704649444710.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=andrew.gospodarek@broadcom.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pavan.chebbi@broadcom.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