From: Jason Gunthorpe <jgg@ziepe.ca>
To: Pavan Chebbi <pavan.chebbi@broadcom.com>
Cc: michael.chan@broadcom.com, linux-kernel@vger.kernel.org,
dave.jiang@intel.com, saeedm@nvidia.com,
Jonathan.Cameron@huawei.com, gospo@broadcom.com,
selvin.xavier@broadcom.com, leon@kernel.org,
kalesh-anakkur.purayil@broadcom.com
Subject: Re: [PATCH v6 fwctl 0/5] fwctl/bnxt_fwctl: fwctl for Broadcom Netxtreme devices
Date: Fri, 27 Mar 2026 09:27:28 -0300 [thread overview]
Message-ID: <20260327122728.GC246076@ziepe.ca> (raw)
In-Reply-To: <20260314151605.932749-1-pavan.chebbi@broadcom.com>
On Sat, Mar 14, 2026 at 08:16:00AM -0700, Pavan Chebbi wrote:
> Introducing bnxt_fwctl which follows along Jason's work [1].
> It is an aux bus driver that enables fwctl for Broadcom
> NetXtreme 574xx, 575xx and 576xx series chipsets by using
> bnxt driver's capability to talk to devices' firmware.
> Pavan Chebbi (5):
> fwctl/bnxt_en: Move common definitions to include/linux/bnxt/
> fwctl/bnxt_en: Refactor aux bus functions to be more generic
> fwctl/bnxt_en: Create an aux device for fwctl
> fwctl/bnxt_fwctl: Add bnxt fwctl device
> fwctl/bnxt_fwctl: Add documentation entries
Appled, thanks
Jason
prev parent reply other threads:[~2026-03-27 12:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-14 15:16 Pavan Chebbi
2026-03-14 15:16 ` [PATCH v6 fwctl 1/5] fwctl/bnxt_en: Move common definitions to include/linux/bnxt/ Pavan Chebbi
2026-03-14 15:16 ` [PATCH v6 fwctl 2/5] fwctl/bnxt_en: Refactor aux bus functions to be more generic Pavan Chebbi
2026-03-14 15:16 ` [PATCH v6 fwctl 3/5] fwctl/bnxt_en: Create an aux device for fwctl Pavan Chebbi
2026-03-14 15:16 ` [PATCH v6 fwctl 4/5] fwctl/bnxt_fwctl: Add bnxt fwctl device Pavan Chebbi
2026-03-14 15:16 ` [PATCH v6 fwctl 5/5] fwctl/bnxt_fwctl: Add documentation entries Pavan Chebbi
2026-03-27 12:27 ` Jason Gunthorpe [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=20260327122728.GC246076@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=Jonathan.Cameron@huawei.com \
--cc=dave.jiang@intel.com \
--cc=gospo@broadcom.com \
--cc=kalesh-anakkur.purayil@broadcom.com \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.chan@broadcom.com \
--cc=pavan.chebbi@broadcom.com \
--cc=saeedm@nvidia.com \
--cc=selvin.xavier@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
all inboxes | Powered by JetHome®