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/2] rxrpc: More fixes
Date: Wed, 24 Aug 2016 09:44:42 -0700 (PDT) [thread overview]
Message-ID: <20160824.094442.37828048887013492.davem@davemloft.net> (raw)
In-Reply-To: <147205078637.13418.9976056129378485689.stgit@warthog.procyon.org.uk>
From: David Howells <dhowells@redhat.com>
Date: Wed, 24 Aug 2016 15:59:46 +0100
> Tagged thusly:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git
> rxrpc-rewrite-20160824-1
Both -1 and -2 pulled, thanks David!
prev parent reply other threads:[~2016-08-24 16:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-24 14:59 [PATCH net-next 0/2] rxrpc: More fixes David Howells
2016-08-24 14:59 ` [PATCH net-next 1/2] rxrpc: Fix conn-based retransmit David Howells
2016-08-24 15:00 ` [PATCH net-next 2/2] rxrpc: Make /proc/net/rxrpc_calls safer David Howells
2016-08-24 16:44 ` 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=20160824.094442.37828048887013492.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).