From: patchwork-bot+netdevbpf@kernel.org
To: Saeed Mahameed <saeed@kernel.org>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
edumazet@google.com, saeedm@nvidia.com, netdev@vger.kernel.org,
tariqt@nvidia.com, linux-hwmon@vger.kernel.org,
jdelvare@suse.com, linux@roeck-us.net
Subject: Re: [PATCH net-next V2 0/2] mlx5: Expose NIC temperature via hwmon API
Date: Wed, 09 Aug 2023 23:00:24 +0000 [thread overview]
Message-ID: <169162202406.2325.4542344753291198627.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230807180507.22984-1-saeed@kernel.org>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 7 Aug 2023 11:05:05 -0700 you wrote:
> From: Saeed Mahameed <saeedm@nvidia.com>
>
> V1->V2:
> - Remove internal tracker tags
> - Remove sanitized mlx5 sensor names
> - add HWMON dependency in the mlx5 Kconfig
>
> [...]
Here is the summary with links:
- [net-next,V2,1/2] net/mlx5: Expose port.c/mlx5_query_module_num() function
https://git.kernel.org/netdev/net-next/c/383a4de3b447
- [net-next,V2,2/2] net/mlx5: Expose NIC temperature via hardware monitoring kernel API
https://git.kernel.org/netdev/net-next/c/1f507e80c700
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:[~2023-08-09 23:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-07 18:05 [PATCH net-next V2 0/2] mlx5: Expose NIC temperature via hwmon API Saeed Mahameed
2023-08-07 18:05 ` [PATCH net-next V2 1/2] net/mlx5: Expose port.c/mlx5_query_module_num() function Saeed Mahameed
2023-08-07 18:05 ` [PATCH net-next V2 2/2] net/mlx5: Expose NIC temperature via hardware monitoring kernel API Saeed Mahameed
2023-08-09 17:54 ` Guenter Roeck
2023-08-08 20:07 ` [PATCH net-next V2 0/2] mlx5: Expose NIC temperature via hwmon API Simon Horman
2023-08-09 23: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=169162202406.2325.4542344753291198627.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jdelvare@suse.com \
--cc=kuba@kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=saeed@kernel.org \
--cc=saeedm@nvidia.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).