From: David Miller <davem@davemloft.net>
To: dhowells@redhat.com
Cc: netdev@vger.kernel.org, linux-afs@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 00/10] rxrpc: Development
Date: Wed, 01 Aug 2018 11:52:24 -0700 (PDT) [thread overview]
Message-ID: <20180801.115224.2067576726634763097.davem@davemloft.net> (raw)
In-Reply-To: <153312832565.27702.15302541876382957550.stgit@warthog.procyon.org.uk>
From: David Howells <dhowells@redhat.com>
Date: Wed, 01 Aug 2018 13:58:45 +0100
>
> Here are some patches that add some more tracepoints to AF_RXRPC and fix
> some issues therein. The most significant points are:
...
> The patches are tagged here:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git
> rxrpc-next-20180801
Pulled, thanks David.
prev parent reply other threads:[~2018-08-01 18:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-01 12:58 [PATCH net-next 00/10] rxrpc: Development David Howells
2018-08-01 12:58 ` [PATCH net-next 01/10] rxrpc: remove redundant variables 'sp' and 'did_discard' David Howells
2018-08-01 12:58 ` [PATCH net-next 02/10] rxrpc: Display call expect-receive-by timeout in proc David Howells
2018-08-01 12:59 ` [PATCH net-next 03/10] rxrpc: Show some more information through /proc files David Howells
2018-08-01 12:59 ` [PATCH net-next 04/10] rxrpc: Fix the trace for terminal ACK (re)transmission David Howells
2018-08-01 12:59 ` [PATCH net-next 05/10] rxrpc: Trace packet transmission David Howells
2018-08-01 12:59 ` [PATCH net-next 06/10] rxrpc: Fix ACK proposal tracepoint David Howells
2018-08-01 12:59 ` [PATCH net-next 07/10] rxrpc: Trace socket notification David Howells
2018-08-01 12:59 ` [PATCH net-next 08/10] rxrpc: Increase the size of a call's Rx window David Howells
2018-08-01 12:59 ` [PATCH net-next 09/10] rxrpc: Propose, but don't immediately transmit, the final ACK for a call David Howells
2018-08-01 12:59 ` [PATCH net-next 10/10] rxrpc: Transmit more ACKs during data reception David Howells
2018-08-01 18:52 ` David Miller [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=20180801.115224.2067576726634763097.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=linux-afs@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--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