From: Benny Halevy <bhalevy@panasas.com>
To: "J. Bruce Fields" <bfields@citi.umich.edu>
Cc: linux-fsdevel@vger.kernel.org, pnfs@linux-nfs.org
Subject: Re: [pnfs] create_session bugfix
Date: Tue, 03 Nov 2009 08:25:49 +0200 [thread overview]
Message-ID: <4AEFCCED.6050007@panasas.com> (raw)
In-Reply-To: <1256684862-14390-1-git-send-email-bfields@citi.umich.edu>
On Oct. 28, 2009, 1:07 +0200, "J. Bruce Fields" <bfields@citi.umich.edu> wrote:
> I'm queueing this up for 2.6.33 if there's no objections.
I've merged both patches also into the pnfs tree so they
get more soak time.
Thanks!
Benny
>
> --b.
> _______________________________________________
> pNFS mailing list
> pNFS@linux-nfs.org
> http://linux-nfs.org/cgi-bin/mailman/listinfo/pnfs
prev parent reply other threads:[~2009-11-03 6:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-27 23:07 create_session bugfix J. Bruce Fields
2009-10-27 23:07 ` [PATCH 1/2] nfsd4.1: fix session memory use calculation J. Bruce Fields
2009-10-27 23:07 ` [PATCH 2/2] nfsd4.1: common slot allocation size calculation J. Bruce Fields
2009-10-27 23:10 ` [pnfs] create_session bugfix J. Bruce Fields
2009-11-03 6:25 ` Benny Halevy [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=4AEFCCED.6050007@panasas.com \
--to=bhalevy@panasas.com \
--cc=bfields@citi.umich.edu \
--cc=linux-fsdevel@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;
as well as URLs for NNTP newsgroup(s).