From: Paolo Abeni <pabeni@redhat.com>
To: David Howells <dhowells@redhat.com>
Cc: netdev@vger.kernel.org, Marc Dionne <marc.dionne@auristor.com>,
Jakub Kicinski <kuba@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
linux-afs@lists.infradead.org, linux-kernel@vger.kernel.org,
Simon Horman <horms@kernel.org>
Subject: Re: [PATCH net 2/2] rxrpc: Fix the rxrpc_connection attend queue handling
Date: Tue, 4 Feb 2025 15:34:37 +0100 [thread overview]
Message-ID: <aa464cc9-7259-4745-bc9a-45b34cf66a60@redhat.com> (raw)
In-Reply-To: <549953.1738678165@warthog.procyon.org.uk>
On 2/4/25 3:09 PM, David Howells wrote:
> Paolo Abeni <pabeni@redhat.com> wrote:
>
>> A couple of minor nits: I think this deserves a 'Fixes' tag,
>
> Fixes: f2cce89a074e ("rxrpc: Implement a mechanism to send an event notification to a connection")
>
>> and possibly split into separate patches to address the reported problems
>> individually.
>
> I can do that if you really want.
I guess we are all better off without the need for a repost. I'm
applying it as-is.
/P
next prev parent reply other threads:[~2025-02-04 14:34 UTC|newest]
Thread overview: 9+ 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-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 [this message]
2025-02-04 15:46 ` David Howells
2025-02-04 10:39 ` [PATCH net 1/2] rxrpc: Fix call state set to not include the SERVER_SECURING state David Howells
2025-02-04 14:40 ` [PATCH net 0/2] rxrpc: Miscellaneous fixes 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=aa464cc9-7259-4745-bc9a-45b34cf66a60@redhat.com \
--to=pabeni@redhat.com \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--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 \
/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;
as well as URLs for NNTP newsgroup(s).