From: ALOK TIWARI <alok.a.tiwari@oracle.com>
To: Bhargava Chenna Marreddy <bhargava.marreddy@broadcom.com>
Cc: Vikas Gupta <vikas.gupta@broadcom.com>,
rajashekar.hudumula@broadcom.com, netdev@vger.kernel.org,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com
Subject: Re: [PATCH net-next] bng_en: fix misleading error message for generic firmware version
Date: Fri, 30 Jan 2026 19:10:13 +0530 [thread overview]
Message-ID: <c19fdbaf-e179-4bbd-b51e-4de154233776@oracle.com> (raw)
In-Reply-To: <CANXQDtbG9cXkzAPoDF9p5sLon=4aOrKJQvojgbieyhQ=+8mWuA@mail.gmail.com>
On 1/30/2026 6:36 PM, Bhargava Chenna Marreddy wrote:
>> On 1/30/2026 2:05 PM, Vikas Gupta wrote:
>>>> drivers/net/ethernet/broadcom/bnge/bnge_devlink.c | 2 +-
>>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>>>
>>>> diff --git a/drivers/net/ethernet/broadcom/bnge/bnge_devlink.c b/drivers/net/ethernet/broadcom/bnge/bnge_devlink.c
>>>> index a987afebd64d..57db3caabcfb 100644
>>>> --- a/drivers/net/ethernet/broadcom/bnge/bnge_devlink.c
>>>> +++ b/drivers/net/ethernet/broadcom/bnge/bnge_devlink.c
>>>> @@ -221,7 +221,7 @@ static int bnge_devlink_info_get(struct devlink *devlink,
>>>> DEVLINK_INFO_VERSION_GENERIC_FW, buf);
>>>> if (rc) {
>>>> NL_SET_ERR_MSG_MOD(extack,
>>>> - "Failed to set roce firmware version");
>>>> + "Failed to set generic firmware version");
>>> Thanks for fixing. I believe instead of generic, "Failed to set
>>> firmware version" is enough.
>> ACK. will send v2.
> Should this be a candidate for net with a Fixes tag?
I am open to either approach. It does not break functionality, but the
current message can be misleading so I am happy to tag it for net if you
think it’s appropriate.
>
> Thanks,
> Bhargava Marreddy
Thanks,
Alok
next prev parent reply other threads:[~2026-01-30 13:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-30 7:30 [PATCH net-next] bng_en: fix misleading error message for generic firmware version Alok Tiwari
2026-01-30 8:35 ` Vikas Gupta
2026-01-30 8:40 ` ALOK TIWARI
2026-01-30 13:06 ` Bhargava Chenna Marreddy
2026-01-30 13:40 ` ALOK TIWARI [this message]
2026-01-30 15:52 ` Bhargava Chenna Marreddy
2026-01-31 1:13 ` Jakub Kicinski
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=c19fdbaf-e179-4bbd-b51e-4de154233776@oracle.com \
--to=alok.a.tiwari@oracle.com \
--cc=andrew+netdev@lunn.ch \
--cc=bhargava.marreddy@broadcom.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rajashekar.hudumula@broadcom.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.