netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Tariq Toukan <tariqt@nvidia.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
	edumazet@google.com, andrew+netdev@lunn.ch, shshitrit@nvidia.com,
	gal@nvidia.com, saeedm@nvidia.com, leon@kernel.org,
	netdev@vger.kernel.org, linux-rdma@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 0/4] mlx5: Add sensor name in temperature message
Date: Tue, 18 Feb 2025 00:40:37 +0000	[thread overview]
Message-ID: <173983923749.3583210.12936325771072711787.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250213094641.226501-1-tariqt@nvidia.com>

Hello:

This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Thu, 13 Feb 2025 11:46:37 +0200 you wrote:
> Hi,
> 
> This small series from Shahar adds the sensors names to the temperature
> event messages, in addition to the existing bitmap indicators.
> This improves human readability.
> 
> Series starts with simple refactoring and modifications. The top patch
> adds the sensors names.
> 
> [...]

Here is the summary with links:
  - [net-next,1/4] net/mlx5: Apply rate-limiting to high temperature warning
    https://git.kernel.org/netdev/net-next/c/9dd3d5d258ac
  - [net-next,2/4] net/mlx5: Prefix temperature event bitmap with '0x' for clarity
    https://git.kernel.org/netdev/net-next/c/b9b72ce0f5f4
  - [net-next,3/4] net/mlx5: Modify LSB bitmask in temperature event to include only the first bit
    https://git.kernel.org/netdev/net-next/c/633f16d7e07c
  - [net-next,4/4] net/mlx5: Add sensor name to temperature event message
    https://git.kernel.org/netdev/net-next/c/46fd50cfcc12

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2025-02-18  0:40 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-13  9:46 [PATCH net-next 0/4] mlx5: Add sensor name in temperature message Tariq Toukan
2025-02-13  9:46 ` [PATCH net-next 1/4] net/mlx5: Apply rate-limiting to high temperature warning Tariq Toukan
2025-02-13 10:15   ` Mateusz Polchlopek
2025-02-13  9:46 ` [PATCH net-next 2/4] net/mlx5: Prefix temperature event bitmap with '0x' for clarity Tariq Toukan
2025-02-13 10:33   ` Mateusz Polchlopek
2025-02-13  9:46 ` [PATCH net-next 3/4] net/mlx5: Modify LSB bitmask in temperature event to include only the first bit Tariq Toukan
2025-02-13 12:11   ` Mateusz Polchlopek
2025-02-13  9:46 ` [PATCH net-next 4/4] net/mlx5: Add sensor name to temperature event message Tariq Toukan
2025-02-15 19:29   ` Simon Horman
2025-02-18  0:27     ` Jakub Kicinski
2025-02-19 13:00       ` Tariq Toukan
2025-02-19 15:28         ` Jakub Kicinski
2025-02-20 22:22           ` Saeed Mahameed
2025-02-18  0:40 ` 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=173983923749.3583210.12936325771072711787.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=gal@nvidia.com \
    --cc=kuba@kernel.org \
    --cc=leon@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=saeedm@nvidia.com \
    --cc=shshitrit@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).