From: patchwork-bot+netdevbpf@kernel.org
To: Allison Henderson <achender@kernel.org>
Cc: netdev@vger.kernel.org, linux-rdma@vger.kernel.org,
pabeni@redhat.com, edumazet@google.com, kuba@kernel.org,
horms@kernel.org
Subject: Re: [PATCH net-next v4 0/2] net/rds: restrict the rdma_cm ids to IB devices
Date: Fri, 02 Oct 2026 00:20:08 +0000 [thread overview]
Message-ID: <179090040828.3154315.2324104902480212536.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260927063058.170273-1-achender@kernel.org>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Sat, 26 Sep 2026 23:30:56 -0700 you wrote:
> Hi all,
>
> This is v4 of the rdma_cm id restriction (v1 at [1], v2 at [2], v3 at
> [3]). Patch 1 is the restriction itself; patch 2 is a small follow-on
> the v3 review turned up in the function patch 1 touches.
>
> Patch 1 restricts the listener, the per-connection id and the probe
> id to RDMA_NODE_IB_CA with rdma_restrict_node_type(), so the rdma_cm
> never installs the RDS listener on, or binds an RDS id to, a device
> RDS has no transport for.
>
> [...]
Here is the summary with links:
- [net-next,v4,1/2] net/rds: restrict the rdma_cm ids to IB devices
https://git.kernel.org/netdev/net-next/c/c7fca8aae6fe
- [net-next,v4,2/2] net/rds: log the port a listener actually bound
https://git.kernel.org/netdev/net-next/c/00d77b181866
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-10-02 0:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-27 6:30 [PATCH net-next v4 0/2] net/rds: restrict the rdma_cm ids to IB devices Allison Henderson
2026-09-27 6:30 ` [PATCH net-next v4 1/2] " Allison Henderson
2026-10-01 12:32 ` Simon Horman
2026-09-27 6:30 ` [PATCH net-next v4 2/2] net/rds: log the port a listener actually bound Allison Henderson
2026-10-01 12:32 ` Simon Horman
2026-10-02 0:20 ` 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=179090040828.3154315.2324104902480212536.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=achender@kernel.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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