From: patchwork-bot+netdevbpf@kernel.org
To: Allison Henderson <achender@kernel.org>
Cc: netdev@vger.kernel.org, pabeni@redhat.com, edumazet@google.com,
kuba@kernel.org, horms@kernel.org, linux-rdma@vger.kernel.org,
linux-kselftest@vger.kernel.org, shuah@kernel.org
Subject: Re: [PATCH net-next v3 0/4] selftests: rds: ROCE support follow ups
Date: Fri, 05 Jun 2026 01:40:16 +0000 [thread overview]
Message-ID: <178062361652.3097022.10798618190558791022.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260602050657.26389-1-achender@kernel.org>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 1 Jun 2026 22:06:53 -0700 you wrote:
> Hi all,
>
> This is a follow up series to the "Add ROCE support to rds selftests"
> series. The first patch renames run.sh to rds_run.sh, which provides
> a self-describing name that appears on the netdev CI dashboard.
>
> The second patch addresses a sashiko complaint that I thought was
> worth circling back for. In the patch "pin RDS sockets to their
> intended transport," sockets are pinned to the specific transport they
> are meant to test. By default, socket transports are implicitly
> selected based on the network topology, but it is possible that they
> can fail back to other transports if the underlying connection could
> not be established. So the patch pins them to the intended transport
> to avoid false positives.
>
> [...]
Here is the summary with links:
- [net-next,v3,1/4] selftests: rds: Rename run.sh to rds_run.sh
https://git.kernel.org/netdev/net-next/c/6d05d3cb44c5
- [net-next,v3,2/4] selftests: rds: pin RDS sockets to their intended transport
https://git.kernel.org/netdev/net-next/c/d2e76c5b1418
- [net-next,v3,3/4] selftests: rds: support RDS built as loadable modules
https://git.kernel.org/netdev/net-next/c/c5eb137685f3
- [net-next,v3,4/4] selftests: rds: report missing RDMA prereqs as XFAIL
https://git.kernel.org/netdev/net-next/c/e3ab0affc10f
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-06-05 1:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-02 5:06 [PATCH net-next v3 0/4] selftests: rds: ROCE support follow ups Allison Henderson
2026-06-02 5:06 ` [PATCH net-next v3 1/4] selftests: rds: Rename run.sh to rds_run.sh Allison Henderson
2026-06-02 5:06 ` [PATCH net-next v3 2/4] selftests: rds: pin RDS sockets to their intended transport Allison Henderson
2026-06-02 5:06 ` [PATCH net-next v3 3/4] selftests: rds: support RDS built as loadable modules Allison Henderson
2026-06-02 5:06 ` [PATCH net-next v3 4/4] selftests: rds: report missing RDMA prereqs as XFAIL Allison Henderson
2026-06-05 1:40 ` 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=178062361652.3097022.10798618190558791022.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-kselftest@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@kernel.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