Netdev List
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: Jason Gunthorpe <jgg@ziepe.ca>
Cc: Jonathan Cameron <jonathan.cameron@huawei.com>,
	Pavan Chebbi <pavan.chebbi@broadcom.com>,
	michael.chan@broadcom.com, dave.jiang@intel.com,
	saeedm@nvidia.com, davem@davemloft.net, corbet@lwn.net,
	edumazet@google.com, gospo@broadcom.com, kuba@kernel.org,
	netdev@vger.kernel.org, pabeni@redhat.com, andrew+netdev@lunn.ch,
	selvin.xavier@broadcom.com, kalesh-anakkur.purayil@broadcom.com
Subject: Re: [PATCH net-next v5 5/5] bnxt_fwctl: Add documentation entries
Date: Sun, 2 Nov 2025 12:45:12 +0200	[thread overview]
Message-ID: <20251102104512.GB17533@unreal> (raw)
In-Reply-To: <20251029133635.GM760669@ziepe.ca>

On Wed, Oct 29, 2025 at 10:36:35AM -0300, Jason Gunthorpe wrote:
> On Tue, Oct 28, 2025 at 04:46:51PM +0000, Jonathan Cameron wrote:
> > On Tue, 14 Oct 2025 01:10:33 -0700
> > Pavan Chebbi <pavan.chebbi@broadcom.com> wrote:
> > 
> > > Add bnxt_fwctl to the driver and fwctl documentation pages.
> > > 
> > > Reviewed-by: Andy Gospodarek <gospo@broadcom.com>
> > > Reviewed-by: Dave Jiang <dave.jiang@intel.com>
> > > Signed-off-by: Pavan Chebbi <pavan.chebbi@broadcom.com>
> > 
> > Would be useful to provide a reference to userspace code that is
> > making use of this.
> > 
> > Jason / others, did we ever get the central repo for user space code
> > set up?
> 
> No, we have some fragemented userspace repos at the moment only. I've
> been looking around for someone who'd like to take on the challenge

Once you find that person, contact me, I'll transfer an ownership
for https://github.com/linux-fwctl to him.

Thanks

> 
> Jason

      reply	other threads:[~2025-11-02 10:45 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-14  8:10 [PATCH net-next v5 0/5] bnxt_fwctl: fwctl for Broadcom Netxtreme devices Pavan Chebbi
2025-10-14  8:10 ` [PATCH net-next v5 1/5] bnxt_en: Move common definitions to include/linux/bnxt/ Pavan Chebbi
2025-10-14  8:10 ` [PATCH net-next v5 2/5] bnxt_en: Refactor aux bus functions to be more generic Pavan Chebbi
2025-10-19 12:52   ` Leon Romanovsky
2026-01-15  9:28     ` Pavan Chebbi
2026-01-15 11:00       ` Leon Romanovsky
2026-01-15 12:21         ` Pavan Chebbi
2025-10-14  8:10 ` [PATCH net-next v5 3/5] bnxt_en: Create an aux device for fwctl Pavan Chebbi
2025-10-14  8:10 ` [PATCH net-next v5 4/5] bnxt_fwctl: Add bnxt fwctl device Pavan Chebbi
2025-10-16  0:40   ` Jakub Kicinski
2025-10-28 16:44   ` Jonathan Cameron
2025-10-14  8:10 ` [PATCH net-next v5 5/5] bnxt_fwctl: Add documentation entries Pavan Chebbi
2025-10-28 16:46   ` Jonathan Cameron
2025-10-29 13:36     ` Jason Gunthorpe
2025-11-02 10:45       ` Leon Romanovsky [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=20251102104512.GB17533@unreal \
    --to=leon@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=corbet@lwn.net \
    --cc=dave.jiang@intel.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=gospo@broadcom.com \
    --cc=jgg@ziepe.ca \
    --cc=jonathan.cameron@huawei.com \
    --cc=kalesh-anakkur.purayil@broadcom.com \
    --cc=kuba@kernel.org \
    --cc=michael.chan@broadcom.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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