From: Jiri Pirko <jiri@resnulli.us>
To: David Howells <dhowells@redhat.com>
Cc: netdev@vger.kernel.org, Marc Dionne <marc.dionne@auristor.com>,
linux-afs@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net 00/19] rxrpc: More fixes for I/O thread conversion/SACK table expansion
Date: Mon, 2 Jan 2023 16:32:44 +0100 [thread overview]
Message-ID: <Y7L5HECgjPgLUQXL@nanopsycho> (raw)
In-Reply-To: <2519213.1671798835@warthog.procyon.org.uk>
Fri, Dec 23, 2022 at 01:33:55PM CET, dhowells@redhat.com wrote:
>The patches should all have been labelled for net, not net-next.
For "net"? Why? Net should only be targetted with bugfixes properly
tagged by "Fixes:" tag.
prev parent reply other threads:[~2023-01-02 15:33 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-23 11:59 [PATCH net 00/19] rxrpc: More fixes for I/O thread conversion/SACK table expansion David Howells
2022-12-23 12:00 ` [PATCH net-next 01/19] rxrpc: Fix a couple of potential use-after-frees David Howells
2022-12-23 12:00 ` [PATCH net-next 02/19] rxrpc: Stash the network namespace pointer in rxrpc_local David Howells
2022-12-23 12:00 ` [PATCH net-next 03/19] rxrpc: Make the local endpoint hold a ref on a connected call David Howells
2022-12-23 12:00 ` [PATCH net-next 04/19] rxrpc: Separate call retransmission from other conn events David Howells
2022-12-23 12:00 ` [PATCH net-next 05/19] rxrpc: Only set/transmit aborts in the I/O thread David Howells
2022-12-23 12:00 ` [PATCH net-next 06/19] rxrpc: Only disconnect calls " David Howells
2022-12-23 12:00 ` [PATCH net-next 07/19] rxrpc: Implement a mechanism to send an event notification to a connection David Howells
2022-12-23 12:00 ` [PATCH net-next 08/19] rxrpc: Clean up connection abort David Howells
2022-12-23 12:00 ` [PATCH net-next 09/19] rxrpc: Tidy up abort generation infrastructure David Howells
2022-12-23 12:01 ` [PATCH net-next 10/19] rxrpc: Make the set of connection IDs per local endpoint David Howells
2022-12-23 12:01 ` [PATCH net-next 11/19] rxrpc: Offload the completion of service conn security to the I/O thread David Howells
2022-12-23 12:01 ` [PATCH net-next 12/19] rxrpc: Set up a connection bundle from a call, not rxrpc_conn_parameters David Howells
2022-12-23 12:01 ` [PATCH net-next 13/19] rxrpc: Split out the call state changing functions into their own file David Howells
2022-12-23 12:01 ` [PATCH net-next 14/19] rxrpc: Wrap accesses to get call state to put the barrier in one place David Howells
2022-12-23 12:01 ` [PATCH net-next 15/19] rxrpc: Move call state changes from sendmsg to I/O thread David Howells
2022-12-23 12:01 ` [PATCH net-next 16/19] rxrpc: Move call state changes from recvmsg " David Howells
2022-12-23 12:01 ` [PATCH net-next 17/19] rxrpc: Remove call->state_lock David Howells
2022-12-23 12:01 ` [PATCH net-next 18/19] rxrpc: Move the client conn cache management to the I/O thread David Howells
2022-12-23 12:02 ` [PATCH net-next 19/19] rxrpc: Move client call connection " David Howells
2022-12-23 12:33 ` [PATCH net 00/19] rxrpc: More fixes for I/O thread conversion/SACK table expansion David Howells
2023-01-02 15:32 ` Jiri Pirko [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=Y7L5HECgjPgLUQXL@nanopsycho \
--to=jiri@resnulli.us \
--cc=dhowells@redhat.com \
--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).