From: Simon Horman <simon.horman@corigine•com>
To: Michael Chan <michael.chan@broadcom•com>
Cc: davem@davemloft•net, netdev@vger•kernel.org, edumazet@google•com,
kuba@kernel•org, pabeni@redhat•com, gospo@broadcom•com
Subject: Re: [PATCH net 3/3] bnxt_en: Add missing 200G link speed reporting
Date: Wed, 29 Mar 2023 15:19:19 +0200 [thread overview]
Message-ID: <ZCQ6117Ifa9yfaY9@corigine.com> (raw)
In-Reply-To: <20230329013021.5205-4-michael.chan@broadcom.com>
On Tue, Mar 28, 2023 at 06:30:21PM -0700, Michael Chan wrote:
> bnxt_fw_to_ethtool_speed() is missing the case statement for 200G
> link speed reported by firmware. As a result, ethtool will report
> unknown speed when the firmware reports 200G link speed.
>
> Fixes: 532262ba3b84 ("bnxt_en: ethtool: support PAM4 link speeds up to 200G")
> Signed-off-by: Michael Chan <michael.chan@broadcom•com>
Reviewed-by: Simon Horman <simon.horman@corigine•com>
next prev parent reply other threads:[~2023-03-29 13:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-29 1:30 [PATCH net 0/3] bnxt_en: 3 Bug fixes Michael Chan
2023-03-29 1:30 ` [PATCH net 1/3] bnxt_en: Fix reporting of test result in ethtool selftest Michael Chan
2023-03-29 13:08 ` Simon Horman
2023-03-29 17:34 ` Michael Chan
2023-03-29 1:30 ` [PATCH net 2/3] bnxt_en: Fix typo in PCI id to device description string mapping Michael Chan
2023-03-29 13:08 ` Simon Horman
2023-03-29 1:30 ` [PATCH net 3/3] bnxt_en: Add missing 200G link speed reporting Michael Chan
2023-03-29 13:19 ` Simon Horman [this message]
2023-03-30 4:50 ` [PATCH net 0/3] bnxt_en: 3 Bug fixes patchwork-bot+netdevbpf
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=ZCQ6117Ifa9yfaY9@corigine.com \
--to=simon.horman@corigine$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=gospo@broadcom$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=michael.chan@broadcom$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(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