From: Jakub Kicinski <kuba@kernel.org>
To: Ido Schimmel <idosch@nvidia.com>
Cc: mkubecek@suse.cz, danieller@nvidia.com, netdev@vger.kernel.org,
linux@armlinux.org.uk, andrew@lunn.ch
Subject: Re: [PATCH ethtool-next v2 2/2] cmis: report LOL / LOS / Tx Fault
Date: Tue, 13 Jun 2023 09:48:34 -0700 [thread overview]
Message-ID: <20230613094834.3b2740fc@kernel.org> (raw)
In-Reply-To: <ZIgbdYe289TsKhHi@shredder>
On Tue, 13 Jun 2023 10:32:05 +0300 Ido Schimmel wrote:
> On Mon, Jun 12, 2023 at 10:05:07PM -0700, Jakub Kicinski wrote:
> > Report whether Loss of Lock, of Signal and Tx Faults were detected.
> > Print "None" in case no lane has the problem, and per-lane "Yes" /
> > "No" if at least one of the lanes reports true.
> >
> > Signed-off-by: Jakub Kicinski <kuba@kernel.org>
>
> Reviewed-by: Ido Schimmel <idosch@nvidia.com>
> Tested-by: Ido Schimmel <idosch@nvidia.com>
Thank you!
next prev parent reply other threads:[~2023-06-13 16:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-13 5:05 [PATCH ethtool-next v2 1/2] sff-8636: report LOL / LOS / Tx Fault Jakub Kicinski
2023-06-13 5:05 ` [PATCH ethtool-next v2 2/2] cmis: " Jakub Kicinski
2023-06-13 7:32 ` Ido Schimmel
2023-06-13 16:48 ` Jakub Kicinski [this message]
2023-06-13 7:06 ` [PATCH ethtool-next v2 1/2] sff-8636: " Ido Schimmel
2023-06-14 18:50 ` 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=20230613094834.3b2740fc@kernel.org \
--to=kuba@kernel.org \
--cc=andrew@lunn.ch \
--cc=danieller@nvidia.com \
--cc=idosch@nvidia.com \
--cc=linux@armlinux.org.uk \
--cc=mkubecek@suse.cz \
--cc=netdev@vger.kernel.org \
/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.