From: Greg Banks <gnb@sgi.com>
To: Neil Brown <neilb@suse.de>
Cc: "J. Bruce Fields" <bfields@fieldses.org>, nfs@lists.sourceforge.net
Subject: Re: [RFC, PATCH 3/3] knfsd: Modify write_ports to use svc_find_xprt service
Date: Thu, 11 Oct 2007 15:26:41 +1000 [thread overview]
Message-ID: <20071011052641.GE31422@sgi.com> (raw)
In-Reply-To: <18189.45080.324267.923517@notabene.brown>
On Thu, Oct 11, 2007 at 03:09:44PM +1000, Neil Brown wrote:
> On Wednesday October 10, bfields@fieldses.org wrote:
> >
> > If this isn't all ready by Friday (OK, maybe Monday) then I think we're
> > out of time.
>
> Sorry, when I said "2.6.24-rc1" previously, I was failing to do
> correct addition. I meant 2.6.25-rc1.
>
> I really don't think it is appropriate to submit these for 2.6.24.
> And I cannot see any real need to do that.
>
> Sorry for the confusion.
So we should be aiming for both the server xprt switch *and*
the rdma xprt for .25?
Greg.
--
Greg Banks, R&D Software Engineer, SGI Australian Software Group.
Apparently, I'm Bedevere. Which MPHG character are you?
I don't speak for SGI.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2007-10-11 5:17 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-11 2:23 [RFC, PATCH 0/3] svc: gnb review cleanup for transport switch Tom Tucker
2007-10-11 2:28 ` [RFC, PATCH 1/3] svc: Change sockaddr to sockaddr_storage in svc_create_xprt Tom Tucker
2007-10-11 2:28 ` [RFC,PATCH 2/3] svc: Fix bugs in svc_find_xprt Tom Tucker
2007-10-11 2:29 ` [RFC, PATCH 3/3] knfsd: Modify write_ports to use svc_find_xprt service Tom Tucker
2007-10-11 3:00 ` Neil Brown
2007-10-11 3:46 ` J. Bruce Fields
2007-10-11 5:09 ` Neil Brown
2007-10-11 5:26 ` Greg Banks [this message]
2007-10-11 5:37 ` Neil Brown
2007-10-11 14:56 ` J. Bruce Fields
2007-10-11 5:11 ` Tom Tucker
2007-10-11 15:25 ` J. Bruce Fields
2007-10-11 15:27 ` Tom Tucker
2007-10-11 17:04 ` J. Bruce Fields
2007-10-11 5:25 ` [RFC, PATCH 0/3] svc: gnb review cleanup for transport switch Greg Banks
2007-10-11 17:09 ` J. Bruce Fields
2007-10-11 20:30 ` J. Bruce Fields
2007-10-11 20:53 ` Tom Tucker
2007-10-11 21:14 ` Tom Tucker
2007-10-11 22:04 ` Tom Tucker
2007-10-11 22:08 ` J. Bruce Fields
2007-10-12 15:17 ` Tom Tucker
2007-10-12 15:41 ` J. Bruce Fields
2007-10-12 16:27 ` Tom Tucker
2007-10-12 21:40 ` Tom Tucker
2007-10-12 22:03 ` J. Bruce Fields
2007-10-12 22:30 ` J. Bruce Fields
2007-10-13 3:48 ` J. Bruce Fields
2007-10-13 12:35 ` Tom Tucker
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=20071011052641.GE31422@sgi.com \
--to=gnb@sgi.com \
--cc=bfields@fieldses.org \
--cc=neilb@suse.de \
--cc=nfs@lists.sourceforge.net \
/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