linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Anna Schumaker <Anna.Schumaker@netapp.com>
To: Chuck Lever <chuck.lever@oracle.com>, <trond.myklebust@primarydata.com>
Cc: <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH 0/2] NFS/RDMA bug fixes for v4.8-rc
Date: Tue, 6 Sep 2016 15:38:32 -0400	[thread overview]
Message-ID: <9c236d3c-dcf4-dd61-a017-b07c86193850@Netapp.com> (raw)
In-Reply-To: <20160906151843.4958.84689.stgit@manet.1015granger.net>

Hi Trond,

You can add my:  "Reviewed-by: Anna Schumaker <Anna.Schumaker@Netapp.com>" if you want to take these patches directly for the next bugfix pull request.

Thanks,
Anna

On 09/06/2016 11:22 AM, Chuck Lever wrote:
> Hi Anna, Trond-
> 
> Commit 3d4cf35bd4fa is wrong, as described in the patch description
> of the revert commit below. It was submitted for v4.8, but needs to
> be removed before v4.8 final, to avoid a regression.
> 
> The second patch below addresses the original problem that
> 3d4cf35bd4fa was attempting to fix.
> 
> Would you consider these for v4.8-rc ?
> 
> ---
> 
> Chuck Lever (2):
>       xprtrdma: Revert 3d4cf35bd4fa ("xprtrdma: Reply buffer exhaustion...")
>       xprtrdma: Fix receive buffer accounting
> 
> 
>  net/sunrpc/xprtrdma/verbs.c     |   45 ++++++++++++++++++++++++++++-----------
>  net/sunrpc/xprtrdma/xprt_rdma.h |    1 +
>  2 files changed, 33 insertions(+), 13 deletions(-)
> 
> --
> Chuck Lever
> 


      parent reply	other threads:[~2016-09-06 19:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-06 15:22 [PATCH 0/2] NFS/RDMA bug fixes for v4.8-rc Chuck Lever
2016-09-06 15:22 ` [PATCH 1/2] xprtrdma: Revert 3d4cf35bd4fa ("xprtrdma: Reply buffer exhaustion...") Chuck Lever
2016-09-06 15:22 ` [PATCH 2/2] xprtrdma: Fix receive buffer accounting Chuck Lever
2016-09-06 19:38 ` Anna Schumaker [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=9c236d3c-dcf4-dd61-a017-b07c86193850@Netapp.com \
    --to=anna.schumaker@netapp.com \
    --cc=chuck.lever@oracle.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=trond.myklebust@primarydata.com \
    /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).