From: Jakub Kicinski <kuba@kernel•org>
To: Pavan Chebbi <pavan.chebbi@broadcom•com>
Cc: jgg@ziepe•ca, michael.chan@broadcom•com, dave.jiang@intel•com,
saeedm@nvidia•com, Jonathan.Cameron@huawei•com,
davem@davemloft•net, corbet@lwn•net, edumazet@google•com,
gospo@broadcom•com, netdev@vger•kernel.org, pabeni@redhat•com,
andrew+netdev@lunn•ch, selvin.xavier@broadcom•com,
leon@kernel•org, kalesh-anakkur.purayil@broadcom•com,
Greg Kroah-Hartman <gregkh@linuxfoundation•org>
Subject: Re: [PATCH net-next v5 4/5] bnxt_fwctl: Add bnxt fwctl device
Date: Wed, 15 Oct 2025 17:40:55 -0700 [thread overview]
Message-ID: <20251015174055.390d98e8@kernel.org> (raw)
In-Reply-To: <20251014081033.1175053-5-pavan.chebbi@broadcom.com>
On Tue, 14 Oct 2025 01:10:32 -0700 Pavan Chebbi wrote:
> + case HWRM_VNIC_RSS_CFG:
Gotta be able to configure basic netdev functions for complex debug!
Or whatever the pretend reasons for fwctl were.
And AFAIK all Broadcom NIC tooling is aggressively closed source.
Frankly I have no idea what the rules are supposed to be for merging
code in this joke of a "subsystem". Please stop tagging this with
net-next, it's definitely no going via our tree.
next prev parent reply other threads:[~2025-10-16 0:40 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 [this message]
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
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=20251015174055.390d98e8@kernel.org \
--to=kuba@kernel$(echo .)org \
--cc=Jonathan.Cameron@huawei$(echo .)com \
--cc=andrew+netdev@lunn$(echo .)ch \
--cc=corbet@lwn$(echo .)net \
--cc=dave.jiang@intel$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=gospo@broadcom$(echo .)com \
--cc=gregkh@linuxfoundation$(echo .)org \
--cc=jgg@ziepe$(echo .)ca \
--cc=kalesh-anakkur.purayil@broadcom$(echo .)com \
--cc=leon@kernel$(echo .)org \
--cc=michael.chan@broadcom$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=pavan.chebbi@broadcom$(echo .)com \
--cc=saeedm@nvidia$(echo .)com \
--cc=selvin.xavier@broadcom$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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