From: Jakub Kicinski <kuba@kernel.org>
To: Vikas Gupta <vikas.gupta@broadcom.com>
Cc: Simon Horman <horms@kernel.org>,
davem@davemloft.net, edumazet@google.com, pabeni@redhat.com,
andrew+netdev@lunn.ch, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
Bhargava Chenna Marreddy <bhargava.marreddy@broadcom.com>
Subject: Re: [PATCH net] bnge: Fix typo
Date: Tue, 17 Feb 2026 14:40:34 -0800 [thread overview]
Message-ID: <20260217144034.6f497076@kernel.org> (raw)
In-Reply-To: <CAHLZf_v1R_9egWmHtkq2QttLYrG8FG=-whEQBw8vBLjmhq=RuA@mail.gmail.com>
On Tue, 17 Feb 2026 23:13:47 +0530 Vikas Gupta wrote:
> On Tue, Feb 17, 2026 at 9:26 PM Simon Horman <horms@kernel.org> wrote:
> > On Mon, Feb 16, 2026 at 07:32:35PM +0530, Vikas Gupta wrote:
> > > Fix the HWRM command type and use the appropriate command to reserve
> > > the resources.
> > >
> > > Fixes: 627c67f038d2 ("bng_en: Add resource management support")
> > > Signed-off-by: Vikas Gupta <vikas.gupta@broadcom.com>
> > > Reviewed-by: Bhargava Chenna Marreddy <bhargava.marreddy@broadcom.com>
> >
> > I think this patch could do with a little more explanation.
> > It's not clear to me, at least: what the difference is between
> > HWRM_FUNC_QCFG and HWRM_FUNC_CFG; and why only one of
> > the instances added by the cited patch needs updating.
>
> HWRM_FUNC_CFG is used to reserve resources, whereas HWRM_FUNC_QCFG is intended
> for querying resource information from the firmware.
> Since __bnge_hwrm_reserve_pf_rings() reserves resources for a specific
> PF, the command type
> should be HWRM_FUNC_CFG.
> However, HWRM_FUNC_QCFG was mistakenly used instead.
> Does it clarify?
Yes, please add this to the commit message.
Also please improve the subject. Something like (just a guess):
bnge: fix reserving resources from FW
"fix typo" sounds like you're fixing spelling in a comment, it's not at
all informative :/
prev parent reply other threads:[~2026-02-17 22:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-16 14:02 [PATCH net] bnge: Fix typo Vikas Gupta
2026-02-17 15:56 ` Simon Horman
2026-02-17 17:43 ` Vikas Gupta
2026-02-17 22:40 ` Jakub Kicinski [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=20260217144034.6f497076@kernel.org \
--to=kuba@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=bhargava.marreddy@broadcom.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=vikas.gupta@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