From: David Miller <davem@davemloft.net>
To: idosch@idosch.org
Cc: netdev@vger.kernel.org, kuba@kernel.org, jiri@mellanox.com,
vadimp@mellanox.com, andrew@lunn.ch, popadrian1996@gmail.com,
mlxsw@mellanox.com, idosch@mellanox.com
Subject: Re: [PATCH net-next v2 0/2] mlxsw: Add support for QSFP-DD transceiver type
Date: Tue, 28 Jul 2020 13:28:24 -0700 (PDT) [thread overview]
Message-ID: <20200728.132824.26736374849989473.davem@davemloft.net> (raw)
In-Reply-To: <20200728102016.1960193-1-idosch@idosch.org>
From: Ido Schimmel <idosch@idosch.org>
Date: Tue, 28 Jul 2020 13:20:14 +0300
> From: Ido Schimmel <idosch@mellanox.com>
>
> This patch set from Vadim adds support for Quad Small Form Factor
> Pluggable Double Density (QSFP-DD) modules in mlxsw.
>
> Patch #1 enables dumping of QSFP-DD module information through ethtool.
>
> Patch #2 enables reading of temperature thresholds from QSFP-DD modules
> for hwmon and thermal zone purposes.
>
> Changes since v1 [1]:
>
> Only rebase on top of net-next. After discussing with Andrew and Adrian
> we agreed that current approach is OK and that in the future we can
> follow Andrew's suggestion to "make a new API where user space can
> request any pages it want, and specify the size of the page". This
> should allow us "to work around known issues when manufactures get their
> EEPROM wrong".
>
> [1] https://lore.kernel.org/netdev/20200626144724.224372-1-idosch@idosch.org/#t
Series applied, thank you.
prev parent reply other threads:[~2020-07-28 20:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-28 10:20 [PATCH net-next v2 0/2] mlxsw: Add support for QSFP-DD transceiver type Ido Schimmel
2020-07-28 10:20 ` [PATCH net-next v2 1/2] mlxsw: core: Add ethtool support for QSFP-DD transceivers Ido Schimmel
2020-07-28 14:04 ` Andrew Lunn
2020-07-28 10:20 ` [PATCH net-next v2 2/2] mlxsw: core: Add support for temperature thresholds reading " Ido Schimmel
2020-07-28 20:28 ` David Miller [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=20200728.132824.26736374849989473.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=andrew@lunn.ch \
--cc=idosch@idosch.org \
--cc=idosch@mellanox.com \
--cc=jiri@mellanox.com \
--cc=kuba@kernel.org \
--cc=mlxsw@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=popadrian1996@gmail.com \
--cc=vadimp@mellanox.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.