All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Stanislav Fomichev <stfomichev@gmail.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com, skalluru@marvell.com,
	manishc@marvell.com, andrew+netdev@lunn.ch,
	michael.chan@broadcom.com, pavan.chebbi@broadcom.com,
	ajit.khaparde@broadcom.com, sriharsha.basavapatna@broadcom.com,
	somnath.kotur@broadcom.com, anthony.l.nguyen@intel.com,
	przemyslaw.kitszel@intel.com, tariqt@nvidia.com,
	saeedm@nvidia.com, louis.peens@corigine.com,
	shshaikh@marvell.com, GR-Linux-NIC-Dev@marvell.com,
	ecree.xilinx@gmail.com, horms@kernel.org, dsahern@kernel.org,
	shuah@kernel.org, tglx@linutronix.de, mingo@kernel.org,
	ruanjinjie@huawei.com, idosch@nvidia.com, razor@blackwall.org,
	petrm@nvidia.com, kuniyu@google.com, sdf@fomichev.me,
	linux-kernel@vger.kernel.org, intel-wired-lan@lists.osuosl.org,
	linux-rdma@vger.kernel.org, oss-drivers@corigine.com,
	linux-net-drivers@amd.com, linux-kselftest@vger.kernel.org,
	leon@kernel.org
Subject: Re: [Intel-wired-lan] [PATCH net-next v5 0/6] udp_tunnel: remove rtnl_lock dependency
Date: Thu, 19 Jun 2025 02:00:18 +0000	[thread overview]
Message-ID: <175029841848.320658.9308379649509683113.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250616162117.287806-1-stfomichev@gmail.com>

Hello:

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

On Mon, 16 Jun 2025 09:21:11 -0700 you wrote:
> Recently bnxt had to grow back a bunch of rtnl dependencies because
> of udp_tunnel's infra. Add separate (global) mutext to protect
> udp_tunnel state.
> 
> v5:
> - remove unused variable (lkp@intel.com)
> 
> [...]

Here is the summary with links:
  - [net-next,v5,1/6] geneve: rely on rtnl lock in geneve_offload_rx_ports
    https://git.kernel.org/netdev/net-next/c/3e14960f3bd2
  - [net-next,v5,2/6] vxlan: drop sock_lock
    https://git.kernel.org/netdev/net-next/c/df5425b3bd85
  - [net-next,v5,3/6] udp_tunnel: remove rtnl_lock dependency
    https://git.kernel.org/netdev/net-next/c/1ead7501094c
  - [net-next,v5,4/6] net: remove redundant ASSERT_RTNL() in queue setup functions
    https://git.kernel.org/netdev/net-next/c/3a321b6b1f76
  - [net-next,v5,5/6] netdevsim: remove udp_ports_sleep
    https://git.kernel.org/netdev/net-next/c/e054c8ba3bce
  - [net-next,v5,6/6] Revert "bnxt_en: bring back rtnl_lock() in the bnxt_open() path"
    https://git.kernel.org/netdev/net-next/c/850d9248d2ea

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



WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+netdevbpf@kernel.org
To: Stanislav Fomichev <stfomichev@gmail.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com, skalluru@marvell.com,
	manishc@marvell.com, andrew+netdev@lunn.ch,
	michael.chan@broadcom.com, pavan.chebbi@broadcom.com,
	ajit.khaparde@broadcom.com, sriharsha.basavapatna@broadcom.com,
	somnath.kotur@broadcom.com, anthony.l.nguyen@intel.com,
	przemyslaw.kitszel@intel.com, tariqt@nvidia.com,
	saeedm@nvidia.com, louis.peens@corigine.com,
	shshaikh@marvell.com, GR-Linux-NIC-Dev@marvell.com,
	ecree.xilinx@gmail.com, horms@kernel.org, dsahern@kernel.org,
	shuah@kernel.org, tglx@linutronix.de, mingo@kernel.org,
	ruanjinjie@huawei.com, idosch@nvidia.com, razor@blackwall.org,
	petrm@nvidia.com, kuniyu@google.com, sdf@fomichev.me,
	linux-kernel@vger.kernel.org, intel-wired-lan@lists.osuosl.org,
	linux-rdma@vger.kernel.org, oss-drivers@corigine.com,
	linux-net-drivers@amd.com, linux-kselftest@vger.kernel.org,
	leon@kernel.org
Subject: Re: [PATCH net-next v5 0/6] udp_tunnel: remove rtnl_lock dependency
Date: Thu, 19 Jun 2025 02:00:18 +0000	[thread overview]
Message-ID: <175029841848.320658.9308379649509683113.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250616162117.287806-1-stfomichev@gmail.com>

Hello:

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

On Mon, 16 Jun 2025 09:21:11 -0700 you wrote:
> Recently bnxt had to grow back a bunch of rtnl dependencies because
> of udp_tunnel's infra. Add separate (global) mutext to protect
> udp_tunnel state.
> 
> v5:
> - remove unused variable (lkp@intel.com)
> 
> [...]

Here is the summary with links:
  - [net-next,v5,1/6] geneve: rely on rtnl lock in geneve_offload_rx_ports
    https://git.kernel.org/netdev/net-next/c/3e14960f3bd2
  - [net-next,v5,2/6] vxlan: drop sock_lock
    https://git.kernel.org/netdev/net-next/c/df5425b3bd85
  - [net-next,v5,3/6] udp_tunnel: remove rtnl_lock dependency
    https://git.kernel.org/netdev/net-next/c/1ead7501094c
  - [net-next,v5,4/6] net: remove redundant ASSERT_RTNL() in queue setup functions
    https://git.kernel.org/netdev/net-next/c/3a321b6b1f76
  - [net-next,v5,5/6] netdevsim: remove udp_ports_sleep
    https://git.kernel.org/netdev/net-next/c/e054c8ba3bce
  - [net-next,v5,6/6] Revert "bnxt_en: bring back rtnl_lock() in the bnxt_open() path"
    https://git.kernel.org/netdev/net-next/c/850d9248d2ea

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-06-19  1:59 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-16 16:21 [Intel-wired-lan] [PATCH net-next v5 0/6] udp_tunnel: remove rtnl_lock dependency Stanislav Fomichev
2025-06-16 16:21 ` Stanislav Fomichev
2025-06-16 16:21 ` [Intel-wired-lan] [PATCH net-next v5 1/6] geneve: rely on rtnl lock in geneve_offload_rx_ports Stanislav Fomichev
2025-06-16 16:21   ` Stanislav Fomichev
2025-06-18 15:14   ` [Intel-wired-lan] " Nikolay Aleksandrov
2025-06-18 15:14     ` Nikolay Aleksandrov
2025-06-16 16:21 ` [Intel-wired-lan] [PATCH net-next v5 2/6] vxlan: drop sock_lock Stanislav Fomichev
2025-06-16 16:21   ` Stanislav Fomichev
2025-06-18  8:24   ` [Intel-wired-lan] " Ido Schimmel
2025-06-18  8:24     ` Ido Schimmel
2025-06-18 15:13   ` [Intel-wired-lan] " Nikolay Aleksandrov
2025-06-18 15:13     ` Nikolay Aleksandrov
2025-06-16 16:21 ` [Intel-wired-lan] [PATCH net-next v5 3/6] udp_tunnel: remove rtnl_lock dependency Stanislav Fomichev
2025-06-16 16:21   ` Stanislav Fomichev
2025-06-16 16:21 ` [Intel-wired-lan] [PATCH net-next v5 4/6] net: remove redundant ASSERT_RTNL() in queue setup functions Stanislav Fomichev
2025-06-16 16:21   ` Stanislav Fomichev
2025-06-16 16:21 ` [Intel-wired-lan] [PATCH net-next v5 5/6] netdevsim: remove udp_ports_sleep Stanislav Fomichev
2025-06-16 16:21   ` Stanislav Fomichev
2025-06-16 16:21 ` [Intel-wired-lan] [PATCH net-next v5 6/6] Revert "bnxt_en: bring back rtnl_lock() in the bnxt_open() path" Stanislav Fomichev
2025-06-16 16:21   ` Stanislav Fomichev
2025-06-19  2:00 ` patchwork-bot+netdevbpf [this message]
2025-06-19  2:00   ` [PATCH net-next v5 0/6] udp_tunnel: remove rtnl_lock dependency patchwork-bot+netdevbpf

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=175029841848.320658.9308379649509683113.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=GR-Linux-NIC-Dev@marvell.com \
    --cc=ajit.khaparde@broadcom.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=anthony.l.nguyen@intel.com \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=ecree.xilinx@gmail.com \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=idosch@nvidia.com \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=kuba@kernel.org \
    --cc=kuniyu@google.com \
    --cc=leon@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-net-drivers@amd.com \
    --cc=linux-rdma@vger.kernel.org \
    --cc=louis.peens@corigine.com \
    --cc=manishc@marvell.com \
    --cc=michael.chan@broadcom.com \
    --cc=mingo@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=oss-drivers@corigine.com \
    --cc=pabeni@redhat.com \
    --cc=pavan.chebbi@broadcom.com \
    --cc=petrm@nvidia.com \
    --cc=przemyslaw.kitszel@intel.com \
    --cc=razor@blackwall.org \
    --cc=ruanjinjie@huawei.com \
    --cc=saeedm@nvidia.com \
    --cc=sdf@fomichev.me \
    --cc=shshaikh@marvell.com \
    --cc=shuah@kernel.org \
    --cc=skalluru@marvell.com \
    --cc=somnath.kotur@broadcom.com \
    --cc=sriharsha.basavapatna@broadcom.com \
    --cc=stfomichev@gmail.com \
    --cc=tariqt@nvidia.com \
    --cc=tglx@linutronix.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.