From: Leon Romanovsky <leonro@nvidia.com>
To: David Ahern <dsahern@kernel.org>
Cc: <stephen@networkplumber.org>, <netdev@vger.kernel.org>,
<linux-rdma@vger.kernel.org>, David Ahern <dahern@nvidia.com>
Subject: Re: [PATCH iproute2-next v2 2/4] iplink: Drop pid fallback code for netns
Date: Wed, 13 May 2026 08:49:38 +0300 [thread overview]
Message-ID: <20260513054938.GA15586@unreal> (raw)
In-Reply-To: <20260512193412.32019-3-dsahern@kernel.org>
On Tue, May 12, 2026 at 01:34:05PM -0600, David Ahern wrote:
> From: David Ahern <dahern@nvidia.com>
>
> Prior commit handles the fallback to pid, so remove
> the now duplicate code from iplink_parse.
>
> Signed-off-by: David Ahern <dahern@nvidia.com>
> ---
> ip/iplink.c | 10 +---------
> 1 file changed, 1 insertion(+), 9 deletions(-)
>
Thanks,
Reviewed-by: Leon Romanovsky <leonro@nvidia.com>
next prev parent reply other threads:[~2026-05-13 5:50 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 [this message]
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 ` [PATCH iproute2-next v2 0/4] Allow rdma dev netns to take a pid 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=20260513054938.GA15586@unreal \
--to=leonro@nvidia.com \
--cc=dahern@nvidia.com \
--cc=dsahern@kernel.org \
--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 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.