Linux NFS development
 help / color / mirror / Atom feed
From: Trond Myklebust <Trond.Myklebust@netapp.com>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH] NFS: Enable NFSv4 callback server to listen on AF_INET6 sockets
Date: Fri, 17 Oct 2008 09:46:45 -0400	[thread overview]
Message-ID: <1224251205.7722.22.camel@localhost> (raw)
In-Reply-To: <20081016212513.21561.55647.stgit-meopP2rzCrTwdl/1UfZZQIVfYA8g3rJ/@public.gmane.org>

On Thu, 2008-10-16 at 17:41 -0400, Chuck Lever wrote:
> Allow the NFS callback server to listen for requests via an AF_INET6 or
> AF_INET socket when IPv6 support is present in the kernel.
> 
> Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
> ---
> 
> I just pulled from your origin/master branch, and this patch appears to
> be missing from the 2.6.28 merge.  The patch was posted originally in
> late August to linux-nfs.
> 
>   http://marc.info/?l=linux-nfs&m=121987073015249&w=2
> 
> Bruce took the others in that series, but I think he may have left this
> one for you since it hits only the client.

I didn't take it at the time because it wouldn't even apply, let alone
compile, without commit e851db5b05408b89b9a9429a66814b79fabee2a1.

I'll push it to Linus later today.
-- 
Trond Myklebust
Linux NFS client maintainer

NetApp
Trond.Myklebust@netapp.com
www.netapp.com

  parent reply	other threads:[~2008-10-17 13:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-16 21:41 [PATCH] NFS: Enable NFSv4 callback server to listen on AF_INET6 sockets Chuck Lever
     [not found] ` <20081016212513.21561.55647.stgit-meopP2rzCrTwdl/1UfZZQIVfYA8g3rJ/@public.gmane.org>
2008-10-17 13:46   ` Trond Myklebust [this message]
2008-10-17 15:03     ` Chuck Lever
2008-10-17 18:40       ` 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=1224251205.7722.22.camel@localhost \
    --to=trond.myklebust@netapp.com \
    --cc=chuck.lever@oracle.com \
    --cc=linux-nfs@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