From: David Miller <davem@davemloft.net>
To: dhowells@redhat.com
Cc: netdev@vger.kernel.org, linux-afs@lists.infradead.org,
dan.carpenter@oracle.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 0/4] rxrpc: Fixes
Date: Fri, 14 Oct 2016 10:45:02 -0400 (EDT) [thread overview]
Message-ID: <20161014.104502.1079192449965835276.davem@davemloft.net> (raw)
In-Reply-To: <147637512988.17348.9857198849984467857.stgit@warthog.procyon.org.uk>
From: David Howells <dhowells@redhat.com>
Date: Thu, 13 Oct 2016 17:12:09 +0100
>
> This set of patches contains a bunch of fixes:
>
> (1) Fix use of kunmap() after change from kunmap_atomic() within AFS.
>
> (2) Don't use of ERR_PTR() with an always zero value.
>
> (3) Check the right error when using ip6_route_output().
>
> (4) Be consistent about whether call->operation_ID is BE or CPU-E within
> AFS.
>
> The patches can be found here also:
>
> http://git.kernel.org/cgit/linux/kernel/git/dhowells/linux-fs.git/log/?h=rxrpc-rewrite
>
> Tagged thusly:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git
> rxrpc-rewrite-20161013
Pulled, thanks David.
prev parent reply other threads:[~2016-10-14 14:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-13 16:12 [PATCH net-next 0/4] rxrpc: Fixes David Howells
2016-10-13 16:12 ` [PATCH net 1/4] afs: unmapping the wrong buffer David Howells
2016-10-13 16:12 ` [PATCH net 2/4] rxrpc: Fix checker warning by not passing always-zero value to ERR_PTR() David Howells
2016-10-13 16:12 ` [PATCH net 3/4] rxrpc: Fix checking of error from ip6_route_output() David Howells
2016-10-13 16:12 ` [PATCH net 4/4] afs: call->operation_ID sometimes used as __be32 sometimes as u32 David Howells
2016-10-14 14:45 ` 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=20161014.104502.1079192449965835276.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=dan.carpenter@oracle.com \
--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).