From: patchwork-bot+netdevbpf@kernel.org
To: David Howells <dhowells@redhat.com>
Cc: netdev@vger.kernel.org, marc.dionne@auristor.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, linux-afs@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net 0/3] rxrpc: Timeout handling fixes
Date: Mon, 01 May 2023 06:50:19 +0000 [thread overview]
Message-ID: <168292381974.24254.3122897495393665483.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230428202756.1186269-1-dhowells@redhat.com>
Hello:
This series was applied to netdev/net.git (main)
by David S. Miller <davem@davemloft.net>:
On Fri, 28 Apr 2023 21:27:53 +0100 you wrote:
> Here are three patches to fix timeouts handling in AF_RXRPC:
>
> (1) The hard call timeout should be interpreted in seconds, not
> milliseconds.
>
> (2) Allow a waiting call to be aborted (thereby cancelling the call) in
> the case a signal interrupts sendmsg() and leaves it hanging until it
> is granted a channel on a connection.
>
> [...]
Here is the summary with links:
- [net,1/3] rxrpc: Fix hard call timeout units
https://git.kernel.org/netdev/net/c/0d098d83c5d9
- [net,2/3] rxrpc: Make it so that a waiting process can be aborted
https://git.kernel.org/netdev/net/c/0eb362d25481
- [net,3/3] rxrpc: Fix timeout of a call that hasn't yet been granted a channel
https://git.kernel.org/netdev/net/c/db099c625b13
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:[~2023-05-01 6:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-28 20:27 [PATCH net 0/3] rxrpc: Timeout handling fixes David Howells
2023-04-28 20:27 ` [PATCH net 1/3] rxrpc: Fix hard call timeout units David Howells
2023-04-28 20:27 ` [PATCH net 2/3] rxrpc: Make it so that a waiting process can be aborted David Howells
2023-04-28 20:27 ` [PATCH net 3/3] rxrpc: Fix timeout of a call that hasn't yet been granted a channel David Howells
2023-05-01 6:50 ` 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=168292381974.24254.3122897495393665483.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox