Linux RDMA and InfiniBand development
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: David Ahern <dsahern@kernel.org>
Cc: stephen@networkplumber.org, netdev@vger.kernel.org,
	leonro@nvidia.com, linux-rdma@vger.kernel.org, dahern@nvidia.com
Subject: Re: [PATCH iproute2-next v2 0/4] Allow rdma dev netns to take a pid
Date: Fri, 15 May 2026 19:30:11 +0000	[thread overview]
Message-ID: <177887341139.127669.4836697961792204536.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260512193412.32019-1-dsahern@kernel.org>

Hello:

This series was applied to iproute2/iproute2-next.git (main)
by David Ahern <dsahern@kernel.org>:

On Tue, 12 May 2026 13:34:03 -0600 you wrote:
> From: David Ahern <dahern@nvidia.com>
> 
> Avoid the extra hurdle of creating an entry in /var/run/netns
> and allow the netns argument to be a name or a pid.
> 
> v2
> - update netns_get_fd to handle the pid fallback
> - update devlink code
> 
> [...]

Here is the summary with links:
  - [iproute2-next,v2,1/4] namespace: Add fallback to netns by pid
    https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=d6a1612bacfe
  - [iproute2-next,v2,2/4] iplink: Drop pid fallback code for netns
    https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=22061a6354c0
  - [iproute2-next,v2,3/4] rdma: Allow netns to be specified by pid
    https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=2a8b53446ff5
  - [iproute2-next,v2,4/4] devlink: Drop now duplicate pid fallback for netns
    (no matching commit)

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



      parent reply	other threads:[~2026-05-15 19:29 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-12 19:34 [PATCH iproute2-next v2 0/4] Allow rdma dev netns to take a pid David Ahern
2026-05-12 19:34 ` [PATCH iproute2-next v2 1/4] namespace: Add fallback to netns by pid David Ahern
2026-05-13  5:49   ` Leon Romanovsky
2026-05-12 19:34 ` [PATCH iproute2-next v2 2/4] iplink: Drop pid fallback code for netns David Ahern
2026-05-13  5:49   ` Leon Romanovsky
2026-05-12 19:34 ` [PATCH iproute2-next v2 3/4] rdma: Allow netns to be specified by pid David Ahern
2026-05-13  5:49   ` Leon Romanovsky
2026-05-12 19:34 ` [PATCH iproute2-next v2 4/4] devlink: Drop now duplicate pid fallback for netns David Ahern
2026-05-13  5:40   ` Leon Romanovsky
2026-05-14  1:06     ` David Ahern
2026-05-15 19:30 ` 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=177887341139.127669.4836697961792204536.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=dahern@nvidia.com \
    --cc=dsahern@kernel.org \
    --cc=leonro@nvidia.com \
    --cc=linux-rdma@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=stephen@networkplumber.org \
    /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