From: patchwork-bot+netdevbpf@kernel.org
To: David Howells <dhowells@redhat.com>
Cc: netdev@vger.kernel.org, marc.dionne@auristor.com,
kuba@kernel.org, davem@davemloft.net, edumazet@google.com,
pabeni@redhat.com, linux-afs@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net 0/2] rxrpc: Miscellaneous fixes
Date: Tue, 04 Feb 2025 14:40:32 +0000 [thread overview]
Message-ID: <173868003201.17912.9717325856767438818.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250203110307.7265-1-dhowells@redhat.com>
Hello:
This series was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Mon, 3 Feb 2025 11:03:02 +0000 you wrote:
> Here some miscellaneous fixes for AF_RXRPC:
>
> (1) Fix the state of a call to not treat the challenge-response cycle as
> part of an incoming call's state set. The problem is that it makes
> handling received of the final packet in the receive phase difficult
> as that wants to change the call state - but security negotiations may
> not yet be complete.
>
> [...]
Here is the summary with links:
- [net,1/2] rxrpc: Fix call state set to not include the SERVER_SECURING state
(no matching commit)
- [net,2/2] rxrpc: Fix the rxrpc_connection attend queue handling
https://git.kernel.org/netdev/net/c/4241a702e0d0
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2025-02-04 14:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-03 11:03 [PATCH net 0/2] rxrpc: Miscellaneous fixes David Howells
2025-02-03 11:03 ` [PATCH net 1/2] rxrpc: Fix call state set to not include the SERVER_SECURING state David Howells
2025-02-04 10:39 ` David Howells
2025-02-03 11:03 ` [PATCH net 2/2] rxrpc: Fix the rxrpc_connection attend queue handling David Howells
2025-02-04 11:12 ` Paolo Abeni
2025-02-04 14:09 ` David Howells
2025-02-04 14:34 ` Paolo Abeni
2025-02-04 15:46 ` David Howells
2025-02-04 14:40 ` patchwork-bot+netdevbpf [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-07-07 10:24 [PATCH net 0/2] rxrpc: Miscellaneous fixes David Howells
2025-07-08 20:20 ` patchwork-bot+netdevbpf
2024-10-01 13:26 David Howells
2024-10-03 23:40 ` patchwork-bot+netdevbpf
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=173868003201.17912.9717325856767438818.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-afs@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.dionne@auristor.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.