Linux NFS development
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: trond.myklebust@netapp.com, linux-nfs@vger.kernel.org
Subject: Re: [PATCH 0/7] Register kernel RPC services via rpcbind v4
Date: Wed, 20 Aug 2008 19:20:02 -0400	[thread overview]
Message-ID: <20080820232002.GA28617@fieldses.org> (raw)
In-Reply-To: <20080818233128.1214.48603.stgit-meopP2rzCrTwdl/1UfZZQIVfYA8g3rJ/@public.gmane.org>

On Mon, Aug 18, 2008 at 07:33:20PM -0400, Chuck Lever wrote:
> Hi Bruce, Trond-
> 
> Here's the patch series that adds rpcbind v4 support to svc_register(), with
> the simplification we discussed last week.  I think this looks cleaner.
> 
> Please consider these for 2.6.28.

Thanks. I've applied #5, #6, and 37 (#2, #3, and #4 were already
applied--let me know if my versions are out of date--and #1 I'll leave
to Trond):

	git://linux-nfs.org/~bfields/linux.git for-2.6.28

Keep sending patches....

--b.


> 
> ---
> 
> Chuck Lever (7):
>       SUNRPC: Support IPv6 when registering kernel RPC services
>       SUNRPC: Split portmap unregister API into separate function
>       SUNRPC: Simplify rpcb_register() API
>       SUNRPC: Use proper INADDR_ANY when setting up RPC services on IPv6
>       SUNRPC: Set V6ONLY socket option for RPC listener sockets
>       SUNRPC: Add address family field to svc_serv data structure
>       NFS: nfs_parsed_mount_options can use unsigned int
> 
> 
>  fs/Kconfig                  |   22 +++++
>  fs/lockd/svc.c              |    2 
>  fs/nfs/callback.c           |    3 -
>  fs/nfs/internal.h           |    8 +-
>  fs/nfsd/nfssvc.c            |    3 -
>  include/linux/sunrpc/clnt.h |    4 -
>  include/linux/sunrpc/svc.h  |   15 ++--
>  net/sunrpc/rpcb_clnt.c      |   65 +++++++---------
>  net/sunrpc/svc.c            |  175 ++++++++++++++++++++++++++++++++++++-------
>  net/sunrpc/svc_xprt.c       |   37 +++++++--
>  net/sunrpc/svcsock.c        |   13 +++
>  11 files changed, 260 insertions(+), 87 deletions(-)
> 
> -- 
> Chuck Lever

      parent reply	other threads:[~2008-08-20 23:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-18 23:33 [PATCH 0/7] Register kernel RPC services via rpcbind v4 Chuck Lever
     [not found] ` <20080818233128.1214.48603.stgit-meopP2rzCrTwdl/1UfZZQIVfYA8g3rJ/@public.gmane.org>
2008-08-18 23:33   ` [PATCH 1/7] NFS: nfs_parsed_mount_options can use unsigned int Chuck Lever
2008-08-18 23:33   ` [PATCH 2/7] SUNRPC: Add address family field to svc_serv data structure Chuck Lever
2008-08-18 23:33   ` [PATCH 3/7] SUNRPC: Set V6ONLY socket option for RPC listener sockets Chuck Lever
2008-08-18 23:33   ` [PATCH 4/7] SUNRPC: Use proper INADDR_ANY when setting up RPC services on IPv6 Chuck Lever
2008-08-18 23:34   ` [PATCH 5/7] SUNRPC: Simplify rpcb_register() API Chuck Lever
2008-08-18 23:34   ` [PATCH 6/7] SUNRPC: Split portmap unregister API into separate function Chuck Lever
2008-08-18 23:34   ` [PATCH 7/7] SUNRPC: Support IPv6 when registering kernel RPC services Chuck Lever
2008-08-20 23:20   ` J. Bruce Fields [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=20080820232002.GA28617@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=chuck.lever@oracle.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=trond.myklebust@netapp.com \
    /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