From: Chuck Lever <chuck.lever@oracle.com>
To: bfields@fieldses.org
Cc: linux-nfs@vger.kernel.org
Subject: [PATCH 0/5] Repost of remaining server-side IPv6 patches
Date: Tue, 26 Jan 2010 14:03:38 -0500 [thread overview]
Message-ID: <20100126190214.3368.89388.stgit@localhost.localdomain> (raw)
Hi Bruce-
Repost of last week's IPv6 patch set. I've attempted to address your
comments.
---
Aime Le Rouzic (1):
NFSD: Support AF_INET6 in svc_addsock() function
Chuck Lever (4):
NFSD: Create PF_INET6 listener in write_ports
SUNRPC: NFS kernel APIs shouldn't return ENOENT for "transport not found"
SUNRPC: Bury "#ifdef IPV6" in svc_create_xprt()
SUNRPC: Use rpc_pton() in ip_map_parse()
fs/lockd/svc.c | 2 --
fs/nfs/callback.c | 2 --
fs/nfsd/nfsctl.c | 24 ++++++++++++++++++-----
net/sunrpc/svc_xprt.c | 9 ++++++++-
net/sunrpc/svcauth_unix.c | 47 +++++++++++++++++++++++++--------------------
net/sunrpc/svcsock.c | 2 +-
6 files changed, 54 insertions(+), 32 deletions(-)
--
Chuck Lever <chuck.lever@oracle.com>
next reply other threads:[~2010-01-26 19:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-26 19:03 Chuck Lever [this message]
[not found] ` <20100126190214.3368.89388.stgit-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2010-01-26 19:03 ` [PATCH 1/5] SUNRPC: Use rpc_pton() in ip_map_parse() Chuck Lever
2010-01-26 19:03 ` [PATCH 2/5] NFSD: Support AF_INET6 in svc_addsock() function Chuck Lever
2010-01-26 19:04 ` [PATCH 3/5] SUNRPC: Bury "#ifdef IPV6" in svc_create_xprt() Chuck Lever
2010-01-26 19:04 ` [PATCH 4/5] SUNRPC: NFS kernel APIs shouldn't return ENOENT for "transport not found" Chuck Lever
2010-01-26 19:04 ` [PATCH 5/5] NFSD: Create PF_INET6 listener in write_ports Chuck Lever
[not found] ` <20100126190422.3368.3981.stgit-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2010-01-26 23:30 ` J. Bruce Fields
2010-01-27 21:18 ` Chuck Lever
2010-01-27 22:04 ` J. Bruce Fields
2010-01-26 23:30 ` [PATCH 0/5] Repost of remaining server-side IPv6 patches 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=20100126190214.3368.89388.stgit@localhost.localdomain \
--to=chuck.lever@oracle.com \
--cc=bfields@fieldses.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.