From: patchwork-bot+netdevbpf@kernel.org
To: Vikas Gupta <vikas.gupta@broadcom.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, andrew+netdev@lunn.ch, horms@kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-rdma@vger.kernel.org, leonro@nvidia.com, jgg@nvidia.com,
michael.chan@broadcom.com, pavan.chebbi@broadcom.com,
andrew.gospodarek@broadcom.com,
vsrama-krishna.nemani@broadcom.com,
rajashekar.hudumula@broadcom.com, ajit.khaparde@broadcom.com,
siva.kallam@broadcom.com, bhargava.marreddy@broadcom.com
Subject: Re: [PATCH net-next v3] bnge/bng_re: Add a new HSI
Date: Wed, 11 Feb 2026 13:00:05 +0000 [thread overview]
Message-ID: <177081480515.167918.7757048918452864142.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260208172925.1861255-1-vikas.gupta@broadcom.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Sun, 8 Feb 2026 22:59:25 +0530 you wrote:
> The HSI is shared between the firmware and the driver and is
> automatically generated.
> Add a new HSI for the BNGE driver. The current HSI refers to BNXT,
> which will become incompatible with ThorUltra devices as the
> BNGE driver adds more features. The BNGE driver will not use the HSI
> located in the bnxt folder.
> Also, add an HSI for ThorUltra RoCE driver.
>
> [...]
Here is the summary with links:
- [net-next,v3] bnge/bng_re: Add a new HSI
https://git.kernel.org/netdev/net-next/c/42d1c54d6248
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:[~2026-02-11 13:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-08 17:29 [PATCH net-next v3] bnge/bng_re: Add a new HSI Vikas Gupta
2026-02-11 13:00 ` 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=177081480515.167918.7757048918452864142.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=ajit.khaparde@broadcom.com \
--cc=andrew+netdev@lunn.ch \
--cc=andrew.gospodarek@broadcom.com \
--cc=bhargava.marreddy@broadcom.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jgg@nvidia.com \
--cc=kuba@kernel.org \
--cc=leonro@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pavan.chebbi@broadcom.com \
--cc=rajashekar.hudumula@broadcom.com \
--cc=siva.kallam@broadcom.com \
--cc=vikas.gupta@broadcom.com \
--cc=vsrama-krishna.nemani@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