From: patchwork-bot+netdevbpf@kernel.org
To: Allison Henderson <achender@kernel.org>
Cc: netdev@vger.kernel.org, linux-kselftest@vger.kernel.org,
pabeni@redhat.com, edumazet@google.com, rds-devel@oss.oracle.com,
kuba@kernel.org, horms@kernel.org, linux-rdma@vger.kernel.org,
allison.henderson@oracle.com
Subject: Re: [PATCH net-next v2 0/2] net/rds: RDS-TCP state machine and message loss improvements
Date: Fri, 23 Jan 2026 21:20:15 +0000 [thread overview]
Message-ID: <176920321584.2718299.3881561780744022977.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260122055213.83608-1-achender@kernel.org>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 21 Jan 2026 22:52:11 -0700 you wrote:
> From: Allison Henderson <allison.henderson@oracle.com>
>
> Hi all,
>
> This is subset 2 of the larger RDS-TCP patch series I posted last
> Oct. The greater series aims to correct multiple rds-tcp issues that
> can cause dropped or out of sequence messages. I've broken it down into
> smaller sets to make reviews more manageable.
>
> [...]
Here is the summary with links:
- [net-next,v2,1/2] net/rds: No shortcut out of RDS_CONN_ERROR
https://git.kernel.org/netdev/net-next/c/ad22d24be635
- [net-next,v2,2/2] net/rds: rds_tcp_accept_one ought to not discard messages
https://git.kernel.org/netdev/net-next/c/db69e9b838c3
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-01-23 21:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-22 5:52 [PATCH net-next v2 0/2] net/rds: RDS-TCP state machine and message loss improvements Allison Henderson
2026-01-22 5:52 ` [PATCH net-next v2 1/2] net/rds: No shortcut out of RDS_CONN_ERROR Allison Henderson
2026-01-22 5:52 ` [PATCH net-next v2 2/2] net/rds: rds_tcp_accept_one ought to not discard messages Allison Henderson
2026-01-23 21: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=176920321584.2718299.3881561780744022977.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=achender@kernel.org \
--cc=allison.henderson@oracle.com \
--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=rds-devel@oss.oracle.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