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 v6 0/2] net/rds: scope-aware sendmsg connection cache
Date: Fri, 23 Oct 2026 22:30:06 +0000 [thread overview]
Message-ID: <179279460632.1302120.16132684698512630001.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261020002816.3087414-1-achender@kernel.org>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 19 Oct 2026 17:28:14 -0700 you wrote:
> Hi all,
>
> This is v6 of the sendmsg connection-cache scope fix (v1 at [1], v2 at
> [2], v3 at [3], v4 at [4], v5 at [5]), against net-next as Jakub
> suggested: neither issue has been observed in the field, and both were
> found by inspection while reworking this cache for the
> connection-lifetime series.
>
> [...]
Here is the summary with links:
- [net-next,v6,1/2] net/rds: include the scope id in the sendmsg connection cache check
https://git.kernel.org/netdev/net/c/b7dfff5e3eb3
- [net-next,v6,2/2] net/rds: keep the connected peer's scope id apart from the bound one
https://git.kernel.org/netdev/net/c/3fe64a5f670d
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-23 22:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-20 0:28 [PATCH net-next v6 0/2] net/rds: scope-aware sendmsg connection cache Allison Henderson
2026-10-20 0:28 ` [PATCH net-next v6 1/2] net/rds: include the scope id in the sendmsg connection cache check Allison Henderson
2026-10-20 0:28 ` [PATCH net-next v6 2/2] net/rds: keep the connected peer's scope id apart from the bound one Allison Henderson
2026-10-23 22:30 ` 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=179279460632.1302120.16132684698512630001.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