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 0/7] rxrpc: Miscellany
Date: Thu, 06 Apr 2017 14:23:09 -0700 (PDT) [thread overview]
Message-ID: <20170406.142309.532616854510026335.davem@davemloft.net> (raw)
In-Reply-To: <149147413410.21583.16278066955827076779.stgit@warthog.procyon.org.uk>
From: David Howells <dhowells@redhat.com>
Date: Thu, 06 Apr 2017 11:22:14 +0100
> Here's a set of patches that make some minor changes to AF_RXRPC:
...
> Tagged thusly:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git
> rxrpc-rewrite-20170406
Pulled, thanks David.
next prev parent reply other threads:[~2017-04-06 21:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-06 10:22 [PATCH net-next 0/7] rxrpc: Miscellany David Howells
2017-04-06 10:22 ` [PATCH net-next 1/7] rxrpc: Use negative error codes in rxrpc_call struct David Howells
2017-04-06 10:22 ` [PATCH net-next 2/7] rxrpc: Note a successfully aborted kernel operation David Howells
2017-04-06 10:22 ` [PATCH net-next 3/7] rxrpc: Handle temporary errors better in rxkad security David Howells
2017-04-06 10:22 ` [PATCH net-next 4/7] rxrpc: Trace protocol errors in received packets David Howells
2017-04-06 10:22 ` [PATCH net-next 5/7] rxrpc: Trace received aborts David Howells
2017-04-06 10:22 ` [PATCH net-next 6/7] rxrpc: Trace changes in a call's receive window size David Howells
2017-04-06 10:23 ` [PATCH net-next 7/7] rxrpc: Trace client call connection David Howells
2017-04-06 21:23 ` David Miller [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-08-29 12:26 [PATCH net-next 0/7] rxrpc: Miscellany David Howells
2017-08-29 16:44 ` David Miller
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=20170406.142309.532616854510026335.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;
as well as URLs for NNTP newsgroup(s).