From: patchwork-bot+netdevbpf@kernel.org
To: =?utf-8?q?Krzysztof_Ol=C4=99dzki_=3Cole=40ans=2Epl=3E?=@ci.codeaurora.org
Cc: tariqt@nvidia.com, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, netdev@vger.kernel.org,
linux-rdma@vger.kernel.org, git@dan.merillat.org,
moshe@nvidia.com, mkubecek@suse.cz, andrew@lunn.ch,
idosch@nvidia.com
Subject: Re: [PATCH v2 net-next] net/mlx4: Add support for EEPROM high pages query for QSFP/QSFP+/QSFP28
Date: Thu, 01 Aug 2024 01:00:32 +0000 [thread overview]
Message-ID: <172247403235.15978.16457678129878308101.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <b17c5336-6dc3-41f2-afa6-f9e79231f224@ans.pl>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 30 Jul 2024 17:49:53 -0700 you wrote:
> Enable reading additional EEPROM information from high pages such as
> thresholds and alarms on QSFP/QSFP+/QSFP28 modules.
>
> "This is similar to commit a708fb7b1f8d ("net/mlx5e: ethtool, Add
> support for EEPROM high pages query") but given all the required logic
> already exists in mlx4_qsfp_eeprom_params_set() only s/_LEN/MAX_LEN/ is
> needed.
>
> [...]
Here is the summary with links:
- [v2,net-next] net/mlx4: Add support for EEPROM high pages query for QSFP/QSFP+/QSFP28
https://git.kernel.org/netdev/net-next/c/9c26a1d0a01c
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2024-08-01 1:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-31 0:49 [PATCH v2 net-next] net/mlx4: Add support for EEPROM high pages query for QSFP/QSFP+/QSFP28 Krzysztof Olędzki
2024-07-31 8:45 ` Ido Schimmel
2024-07-31 13:56 ` Krzysztof Olędzki
2024-08-01 1:00 ` patchwork-bot+netdevbpf [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=172247403235.15978.16457678129878308101.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc==?utf-8?q?Krzysztof_Ol=C4=99dzki_=3Cole=40ans=2Epl=3E?=@ci.codeaurora.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=git@dan.merillat.org \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=mkubecek@suse.cz \
--cc=moshe@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=tariqt@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;
as well as URLs for NNTP newsgroup(s).