From: Jakub Kicinski <kuba@kernel.org>
To: Chris Babroski <cbabroski@nvidia.com>
Cc: <andrew+netdev@lunn.ch>, <davem@davemloft.net>,
<davthompson@nvidia.com>, <edumazet@google.com>,
<hkallweit1@gmail.com>, <linux-kernel@vger.kernel.org>,
<linux@armlinux.org.uk>, <netdev@vger.kernel.org>,
<pabeni@redhat.com>
Subject: Re: [PATCH net-next v2] mlxbf_gige: report unknown speed and duplex when link is down
Date: Wed, 22 Oct 2025 17:09:38 -0700 [thread overview]
Message-ID: <20251022170938.3a9a618e@kernel.org> (raw)
In-Reply-To: <20251022170825.1108218-1-cbabroski@nvidia.com>
On Wed, 22 Oct 2025 13:08:25 -0400 Chris Babroski wrote:
> Hi Jakub,
>
> Thank you for pointing 60f887b1290b out - this commit resolves
> the issue and our patch is no longer needed. Please disregard.
Lucky timing :) Thanks for confirming
prev parent reply other threads:[~2025-10-23 0:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-14 16:16 [PATCH net-next v2] mlxbf_gige: report unknown speed and duplex when link is down Chris Babroski
2025-10-17 22:54 ` Jakub Kicinski
2025-10-22 17:08 ` Chris Babroski
2025-10-23 0:09 ` 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=20251022170938.3a9a618e@kernel.org \
--to=kuba@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=cbabroski@nvidia.com \
--cc=davem@davemloft.net \
--cc=davthompson@nvidia.com \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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;
as well as URLs for NNTP newsgroup(s).