From: patchwork-bot+netdevbpf@kernel.org
To: Allison Henderson <achender@kernel.org>
Cc: netdev@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 v5 0/2] net/rds: RDS-TCP bug fix collection, subset 1: Work queue scalability
Date: Tue, 13 Jan 2026 11:40:13 +0000 [thread overview]
Message-ID: <176830441313.2202748.11246831257261370626.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260109224843.128076-1-achender@kernel.org>
Hello:
This series was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Fri, 9 Jan 2026 15:48:41 -0700 you wrote:
> From: Allison Henderson <allison.henderson@oracle.com>
>
> Hi all,
>
> This is subset 1 of the RDS-TCP bug fix collection series I posted last
> Oct. The greater series aims to correct multiple rds-tcp bugs that
> can cause dropped or out of sequence messages. The set was starting to
> get a bit large, so I've broken it down into smaller sets to make
> reviews more manageable.
>
> [...]
Here is the summary with links:
- [net-next,v5,1/2] net/rds: Add per cp work queue
https://git.kernel.org/netdev/net-next/c/d327e2e74aed
- [net-next,v5,2/2] net/rds: Give each connection path its own workqueue
https://git.kernel.org/netdev/net-next/c/4716af3897e9
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-13 11:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-09 22:48 [PATCH net-next v5 0/2] net/rds: RDS-TCP bug fix collection, subset 1: Work queue scalability Allison Henderson
2026-01-09 22:48 ` [PATCH net-next v5 1/2] net/rds: Add per cp work queue Allison Henderson
2026-01-09 22:48 ` [PATCH net-next v5 2/2] net/rds: Give each connection path its own workqueue Allison Henderson
2026-01-13 11: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=176830441313.2202748.11246831257261370626.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-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