public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Benny Halevy <bhalevy@panasas.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: pnfs@linux-nfs.org, linux-nfs@vger.kernel.org
Subject: Re: [PATCH 37/44] nfsd41: sunrpc: Added rpc server-side	backchannel handling
Date: Tue, 23 Jun 2009 08:47:01 +0300	[thread overview]
Message-ID: <4A406C55.5030008@panasas.com> (raw)
In-Reply-To: <20090622181954.GB19619@fieldses.org>

On Jun. 22, 2009, 21:19 +0300, "J. Bruce Fields" <bfields@fieldses.org> wrote:
> By the way, apologies, I believe these are quite close, but the merge
> window is closing and I need to help with the move, so this will have to
> be queued for 2.6.32.  I'll start doing that as soon as I can.

Sigh, bad timing.
Given the depth of your review we should definitely have had
to start reviewing this code much sooner.

> 
> Also I'm aware there are some more bugfixes that should really go into
> 2.6.31; if I haven't dealt with those by the end of the week, please
> complain.

Thanks.  I'll follow up on that too.

Benny

> 
> --b.

  reply	other threads:[~2009-06-23  5:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-16  1:20 [PATCH 37/44] nfsd41: sunrpc: Added rpc server-side backchannel handling Benny Halevy
2009-06-19 23:10 ` J. Bruce Fields
2009-06-22 12:48   ` Benny Halevy
2009-06-28 16:20     ` [PATCH 1/2] SQUASHME: nfsd41: sunrpc: move struct rpc_buffer def into a common header file Benny Halevy
2009-06-28 16:20     ` [PATCH 2/2] SQUASHME: nfsd41: change bc_sock to bc_xprt Benny Halevy
2009-06-22 18:19 ` [PATCH 37/44] nfsd41: sunrpc: Added rpc server-side backchannel handling J. Bruce Fields
2009-06-23  5:47   ` Benny Halevy [this message]
2009-06-24 20:05     ` J. Bruce Fields

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=4A406C55.5030008@panasas.com \
    --to=bhalevy@panasas.com \
    --cc=bfields@fieldses.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=pnfs@linux-nfs.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