public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
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, moshe@nvidia•com
Subject: Re: [net-next 01/15] net/mlx5: remove redundant clear_bit
Date: Thu, 16 Mar 2023 05:20:20 +0000	[thread overview]
Message-ID: <167894402049.17806.16003249846354613363.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230314054234.267365-2-saeed@kernel.org>

Hello:

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

On Mon, 13 Mar 2023 22:42:20 -0700 you wrote:
> From: Moshe Shemesh <moshe@nvidia•com>
> 
> When shutdown or remove callbacks are called the driver sets the flag
> MLX5_BREAK_FW_WAIT, to stop waiting for FW as teardown was called. There
> is no need to clear the bit as once shutdown or remove were called as
> there is no way back, the driver is going down. Furthermore, if not
> cleared the flag can be used also in other loops where we may wait while
> teardown was already called.
> 
> [...]

Here is the summary with links:
  - [net-next,01/15] net/mlx5: remove redundant clear_bit
    https://git.kernel.org/netdev/net-next/c/c05d145abea1
  - [net-next,02/15] net/mlx5: Stop waiting for PCI up if teardown was triggered
    https://git.kernel.org/netdev/net-next/c/8ff38e730c3f
  - [net-next,03/15] net/mlx5: Add comment to mlx5_devlink_params_register()
    https://git.kernel.org/netdev/net-next/c/ceefcfb8a375
  - [net-next,04/15] net/mlx5: Implement thermal zone
    https://git.kernel.org/netdev/net-next/c/c1fef618d611
  - [net-next,05/15] net/mlx5e: Correct SKB room check to use all room in the fifo
    https://git.kernel.org/netdev/net-next/c/aa98d15ea40b
  - [net-next,06/15] net/mlx5e: Rename RQ/SQ adaptive moderation state flag
    https://git.kernel.org/netdev/net-next/c/2b5bd5b1611b
  - [net-next,07/15] net/mlx5e: Stringify RQ SW state in RQ devlink health diagnostics
    https://git.kernel.org/netdev/net-next/c/1fe7bc109e3e
  - [net-next,08/15] net/mlx5e: Expose SQ SW state as part of SQ health diagnostics
    https://git.kernel.org/netdev/net-next/c/fc9d982a2512
  - [net-next,09/15] net/mlx5e: Add XSK RQ state flag for RQ devlink health diagnostics
    https://git.kernel.org/netdev/net-next/c/bb76d250e55c
  - [net-next,10/15] net/mlx5: Move needed PTYS functions to core layer
    https://git.kernel.org/netdev/net-next/c/028522e28443
  - [net-next,11/15] net/mlx5e: Add devlink hairpin queues parameters
    https://git.kernel.org/netdev/net-next/c/1bffcea42926
  - [net-next,12/15] net/mlx5e: Add more information to hairpin table dump
    https://git.kernel.org/netdev/net-next/c/8a0594c09610
  - [net-next,13/15] net/mlx5e: TC, Extract indr setup block checks to function
    https://git.kernel.org/netdev/net-next/c/244fd698207f
  - [net-next,14/15] net/mlx5e: Enable TC offload for ingress MACVLAN over bond
    https://git.kernel.org/netdev/net-next/c/d5d006bb27ad
  - [net-next,15/15] net/mlx5e: Enable TC offload for egress MACVLAN over bond
    https://git.kernel.org/netdev/net-next/c/63b02048f9a7

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



  reply	other threads:[~2023-03-16  5:20 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-14  5:42 [pull request][net-next 00/15] mlx5 updates 2023-03-13 Saeed Mahameed
2023-03-14  5:42 ` [net-next 01/15] net/mlx5: remove redundant clear_bit Saeed Mahameed
2023-03-16  5:20   ` patchwork-bot+netdevbpf [this message]
2023-03-14  5:42 ` [net-next 02/15] net/mlx5: Stop waiting for PCI up if teardown was triggered Saeed Mahameed
2023-03-14  5:42 ` [net-next 03/15] net/mlx5: Add comment to mlx5_devlink_params_register() Saeed Mahameed
2023-03-14  5:42 ` [net-next 04/15] net/mlx5: Implement thermal zone Saeed Mahameed
2023-03-14  5:42 ` [net-next 05/15] net/mlx5e: Correct SKB room check to use all room in the fifo Saeed Mahameed
2023-03-16  4:56   ` Jakub Kicinski
2023-03-16  4:59     ` Jakub Kicinski
2023-03-16  5:05       ` Saeed Mahameed
2023-03-16  5:13         ` Jakub Kicinski
2023-03-14  5:42 ` [net-next 06/15] net/mlx5e: Rename RQ/SQ adaptive moderation state flag Saeed Mahameed
2023-03-14  5:42 ` [net-next 07/15] net/mlx5e: Stringify RQ SW state in RQ devlink health diagnostics Saeed Mahameed
2023-03-14  5:42 ` [net-next 08/15] net/mlx5e: Expose SQ SW state as part of SQ " Saeed Mahameed
2023-03-14  5:42 ` [net-next 09/15] net/mlx5e: Add XSK RQ state flag for RQ devlink " Saeed Mahameed
2023-03-14  5:42 ` [net-next 10/15] net/mlx5: Move needed PTYS functions to core layer Saeed Mahameed
2023-03-14  5:42 ` [net-next 11/15] net/mlx5e: Add devlink hairpin queues parameters Saeed Mahameed
2023-03-14  5:42 ` [net-next 12/15] net/mlx5e: Add more information to hairpin table dump Saeed Mahameed
2023-03-14  5:42 ` [net-next 13/15] net/mlx5e: TC, Extract indr setup block checks to function Saeed Mahameed
2023-03-14  5:42 ` [net-next 14/15] net/mlx5e: Enable TC offload for ingress MACVLAN over bond Saeed Mahameed
2023-03-14  5:42 ` [net-next 15/15] net/mlx5e: Enable TC offload for egress " Saeed Mahameed

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=167894402049.17806.16003249846354613363.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel$(echo .)org \
    --cc=davem@davemloft$(echo .)net \
    --cc=edumazet@google$(echo .)com \
    --cc=kuba@kernel$(echo .)org \
    --cc=moshe@nvidia$(echo .)com \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=pabeni@redhat$(echo .)com \
    --cc=saeed@kernel$(echo .)org \
    --cc=saeedm@nvidia$(echo .)com \
    --cc=tariqt@nvidia$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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