From: Ido Schimmel <idosch@idosch.org>
To: netdev@vger.kernel.org
Cc: davem@davemloft.net, kuba@kernel.org, jiri@nvidia.com,
andrew@lunn.ch, vladyslavt@nvidia.com, moshe@nvidia.com,
vadimp@nvidia.com, mkubecek@suse.cz, mlxsw@nvidia.com,
Ido Schimmel <idosch@nvidia.com>
Subject: [RFC PATCH ethtool-next 0/2] ethtool: Add ability to write to transceiver module EEPROMs
Date: Wed, 23 Jun 2021 11:08:23 +0300 [thread overview]
Message-ID: <20210623080825.2612270-1-idosch@idosch.org> (raw)
From: Ido Schimmel <idosch@nvidia.com>
Patch #1 updates the UAPI headers.
Patch #2 adds the actual implementation. See the commit message for
example output.
Patches are on top of [1] which are currently under review.
Refer to [2] for more background information.
[1] https://patchwork.kernel.org/project/netdevbpf/cover/1623949504-51291-1-git-send-email-moshe@nvidia.com/
[2] https://patchwork.kernel.org/project/netdevbpf/cover/20210623075925.2610908-1-idosch@idosch.org/
Ido Schimmel (2):
Update UAPI header copies
ethtool: Add ability to write to transceiver module EEPROM
ethtool.8.in | 29 ++++++++
ethtool.c | 10 +++
netlink/desc-ethtool.c | 2 +
netlink/extapi.h | 2 +
netlink/module-eeprom.c | 125 ++++++++++++++++++++++++++++++++++-
netlink/monitor.c | 4 ++
netlink/netlink.h | 1 +
uapi/linux/ethtool.h | 4 +-
uapi/linux/ethtool_netlink.h | 4 +-
uapi/linux/if_link.h | 9 +++
uapi/linux/netlink.h | 5 +-
11 files changed, 188 insertions(+), 7 deletions(-)
--
2.31.1
next reply other threads:[~2021-06-23 8:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-23 8:08 Ido Schimmel [this message]
2021-06-23 8:08 ` [RFC PATCH ethtool-next 1/2] Update UAPI header copies Ido Schimmel
2021-06-23 8:08 ` [RFC PATCH ethtool-next 2/2] ethtool: Add ability to write to transceiver module EEPROM Ido Schimmel
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=20210623080825.2612270-1-idosch@idosch.org \
--to=idosch@idosch.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=idosch@nvidia.com \
--cc=jiri@nvidia.com \
--cc=kuba@kernel.org \
--cc=mkubecek@suse.cz \
--cc=mlxsw@nvidia.com \
--cc=moshe@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=vadimp@nvidia.com \
--cc=vladyslavt@nvidia.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.