From: Ido Schimmel <idosch@nvidia.com>
To: Ivan Vecera <ivecera@redhat.com>
Cc: netdev@vger.kernel.org, Michal Kubecek <mkubecek@suse.cz>,
Daniel Juarez <djuarezg@cern.ch>
Subject: Re: [PATCH ethtool] sff-8079/8472: Fix missing sff-8472 output in netlink path
Date: Thu, 16 Jun 2022 20:34:15 +0300 [thread overview]
Message-ID: <Yqtpl+DLpH/YDnxy@shredder> (raw)
In-Reply-To: <20220616155009.3609572-1-ivecera@redhat.com>
On Thu, Jun 16, 2022 at 05:50:09PM +0200, Ivan Vecera wrote:
> Commit 5b64c66f58d ("ethtool: Add netlink handler for
> getmodule\r (-m)") provided a netlink variant for getmodule
> but also introduced a regression as netlink output is different
> from ioctl output that provides information from A2h page
> via sff8472_show_all().
>
> To fix this the netlink path should check a presence of A2h page
> by value of bit 6 in byte 92 of page A0h and if it is set then
> get A2h page and call sff8472_show_all().
>
> Fixes: 5b64c66f58d ("ethtool: Add netlink handler for getmodule\r (-m)")
> Tested-by: Daniel Juarez <djuarezg@cern.ch>
> Co-authored-by: Ido Schimmel <idosch@nvidia.com>
> Signed-off-by: Ivan Vecera <ivecera@redhat.com>
With Michal's comment:
Reviewed-by: Ido Schimmel <idosch@nvidia.com>
Tested-by: Ido Schimmel <idosch@nvidia.com>
Tested with both netlink and ioctl, but only with SFP modules that lack
diagnostic information, as I don't have these at hand.
Michal, note that for ethtool-next we plan to get rid of sfpdiag.c and
fold it into sfpid.c, so that the latter will be able to handle both
SFF-8079 and SFF-8472 using the same memory map. We felt that it's too
big of a change for the main branch.
next prev parent reply other threads:[~2022-06-16 17:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-16 15:50 [PATCH ethtool] sff-8079/8472: Fix missing sff-8472 output in netlink path Ivan Vecera
2022-06-16 16:19 ` Michal Kubecek
2022-06-16 17:56 ` Ivan Vecera
2022-06-16 17:34 ` Ido Schimmel [this message]
2022-06-16 17:57 ` Ivan Vecera
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=Yqtpl+DLpH/YDnxy@shredder \
--to=idosch@nvidia.com \
--cc=djuarezg@cern.ch \
--cc=ivecera@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox