From: Gal Pressman <gal@nvidia.com>
To: "Krzysztof Olędzki" <ole@ans.pl>,
"Ido Schimmel" <idosch@nvidia.com>,
"Tariq Toukan" <tariqt@nvidia.com>,
"David S. Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
"Jakub Kicinski" <kuba@kernel.org>,
"Paolo Abeni" <pabeni@redhat.com>,
"Saeed Mahameed" <saeedm@nvidia.com>,
"Leon Romanovsky" <leon@kernel.org>,
"Yishai Hadas" <yishaih@nvidia.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
linux-rdma@vger.kernel.org
Subject: Re: [PATCH net-next 1/4] mlx4/mlx5: {mlx4,mlx5e}_en_get_module_info cleanup
Date: Mon, 16 Sep 2024 11:44:25 +0300 [thread overview]
Message-ID: <55ffb761-170b-4a1c-8565-7e6f531d423c@nvidia.com> (raw)
In-Reply-To: <8a0c724e-d2fb-4ae6-bf5d-74bbd0a7581b@ans.pl>
On 16/09/2024 10:30, Krzysztof Olędzki wrote:
> On 16.09.2024 at 00:16, Gal Pressman wrote:
>> Hi Krzysztof,
>
> Hi Gal,
>
> Thank you so much for your prompt review!
>
>> On 12/09/2024 9:38, Krzysztof Olędzki wrote:
>>> Use SFF8024 constants defined in linux/sfp.h instead of private ones.
>>>
>>> Make mlx4_en_get_module_info() and mlx5e_get_module_info() to look
>>> as close as possible to each other.
mlx4 and mlx5 don't necessarily have to be similar to each other.
>>> Simplify the logic for selecting SFF_8436 vs SFF_8636.
This commit message reflects my main issue with this patch, patches
should be concise, this patch tries to achieve (at least) three
different things in one.
>>>
>>> Signed-off-by: Krzysztof Piotr Oledzki <ole@ans.pl>
>>> @@ -2029,33 +2030,35 @@ static int mlx4_en_get_module_info(struct net_device *dev,
>>>
>>> /* Read first 2 bytes to get Module & REV ID */
>>> ret = mlx4_get_module_info(mdev->dev, priv->port,
>>> - 0/*offset*/, 2/*size*/, data);
>>> + 0 /*offset*/, 2 /*size*/, data);
>>
>> Why?
>
> I tried to be consistent with the other places, some examples:
> fw.c: err = mlx4_cmd(dev, mailbox->dma, 0x01 /* subn mgmt class */,
> en_tx.c: 0, 0 /* Non-NAPI caller */);
>
> Would you like me to drop this part of the change?
I didn't see the commit message mention anything about changing coding
style.
>
>>
>>> if (ret < 2)
>>> return -EIO;
>>>
>>> - switch (data[0] /* identifier */) {
>>> - case MLX4_MODULE_ID_QSFP:
>>> - modinfo->type = ETH_MODULE_SFF_8436;
>>> + /* data[0] = identifier byte */
>>> + switch (data[0]) {
>>> + case SFF8024_ID_QSFP_8438:
>>> + modinfo->type = ETH_MODULE_SFF_8436;
>>> modinfo->eeprom_len = ETH_MODULE_SFF_8436_MAX_LEN;
>>> break;
>>> - case MLX4_MODULE_ID_QSFP_PLUS:
>>> - if (data[1] >= 0x3) { /* revision id */
>>> - modinfo->type = ETH_MODULE_SFF_8636;
>>> - modinfo->eeprom_len = ETH_MODULE_SFF_8636_MAX_LEN;
>>> - } else {
>>> - modinfo->type = ETH_MODULE_SFF_8436;
>>> + case SFF8024_ID_QSFP_8436_8636:
>>> + /* data[1] = revision id */
>>> + if (data[1] < 0x3) {
>>> + modinfo->type = ETH_MODULE_SFF_8436;
>>> modinfo->eeprom_len = ETH_MODULE_SFF_8436_MAX_LEN;
>>> + break;
>>> }
>>> - break;
>>> - case MLX4_MODULE_ID_QSFP28:
>>> - modinfo->type = ETH_MODULE_SFF_8636;
>>> + fallthrough;
>>> + case SFF8024_ID_QSFP28_8636:
>>> + modinfo->type = ETH_MODULE_SFF_8636;
>>> modinfo->eeprom_len = ETH_MODULE_SFF_8636_MAX_LEN;
>>> break;
>>> - case MLX4_MODULE_ID_SFP:
>>> - modinfo->type = ETH_MODULE_SFF_8472;
>>> + case SFF8024_ID_SFP:
>>> + modinfo->type = ETH_MODULE_SFF_8472;
>>> modinfo->eeprom_len = ETH_MODULE_SFF_8472_LEN;
>>> break;
>>> default:
>>> + netdev_err(dev, "%s: cable type not recognized: 0x%x\n",
>>> + __func__, data[0]);
>>
>> 0x%x -> %#x.
>
> Ah, sure.
Continuing my previous comment, I didn't see the commit message mention
anything about adding new prints.
next prev parent reply other threads:[~2024-09-16 8:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-12 6:38 [PATCH net-next 1/4] mlx4/mlx5: {mlx4,mlx5e}_en_get_module_info cleanup Krzysztof Olędzki
2024-09-13 20:55 ` Jakub Kicinski
2024-09-14 2:12 ` Krzysztof Olędzki
2024-09-14 2:48 ` Jakub Kicinski
2024-09-14 8:21 ` Simon Horman
2024-09-15 2:21 ` Krzysztof Olędzki
2024-09-16 9:38 ` Przemek Kitszel
2024-09-16 7:16 ` Gal Pressman
2024-09-16 7:30 ` Krzysztof Olędzki
2024-09-16 8:44 ` Gal Pressman [this message]
2024-09-17 4:19 ` Krzysztof Olędzki
2024-09-17 7:04 ` Gal Pressman
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=55ffb761-170b-4a1c-8565-7e6f531d423c@nvidia.com \
--to=gal@nvidia.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=ole@ans.pl \
--cc=pabeni@redhat.com \
--cc=saeedm@nvidia.com \
--cc=tariqt@nvidia.com \
--cc=yishaih@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox