Linux NFS development
 help / color / mirror / Atom feed
From: Steve Dickson <SteveD@redhat.com>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH 0/4] Four more pre-requisites for mountd IPv6 support
Date: Fri, 23 Apr 2010 12:29:48 -0400	[thread overview]
Message-ID: <4BD1CAFC.9080200@RedHat.com> (raw)
In-Reply-To: <20100419201855.3567.9644.stgit@matisse.1015granger.net>



On 04/19/2010 04:20 PM, Chuck Lever wrote:
> Hi Steve-
> 
> These patches clean up some memory allocation nits in libexport.a.
> They pave the way for parsing IPv6 addresses and netmasks in
> client_init().
> 
> ---
> 
> Chuck Lever (4):
>       libexport.a: Allow malloc(3) failures in client_lookup() and friends
>       libexport.a: Allow m_hostname allocation to fail instead of exit
>       libexport.a: Allow client_init() to fail instead of exit
>       libexport.a: Add client_free()
> 
> 
>  support/export/client.c |   55 +++++++++++++++++++++++++++++++----------------
>  1 files changed, 36 insertions(+), 19 deletions(-)
> 
All four committed... 

steved.

      parent reply	other threads:[~2010-04-23 17:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-19 20:20 [PATCH 0/4] Four more pre-requisites for mountd IPv6 support Chuck Lever
     [not found] ` <20100419201855.3567.9644.stgit-RytpoXr2tKZ9HhUboXbp9zCvJB+x5qRC@public.gmane.org>
2010-04-19 20:21   ` [PATCH 1/4] libexport.a: Add client_free() Chuck Lever
2010-04-19 20:21   ` [PATCH 2/4] libexport.a: Allow client_init() to fail instead of exit Chuck Lever
2010-04-19 20:21   ` [PATCH 3/4] libexport.a: Allow m_hostname allocation " Chuck Lever
2010-04-19 20:21   ` [PATCH 4/4] libexport.a: Allow malloc(3) failures in client_lookup() and friends Chuck Lever
2010-04-20 12:16   ` [PATCH 0/4] Four more pre-requisites for mountd IPv6 support Jeff Layton
2010-04-23 16:29 ` Steve Dickson [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=4BD1CAFC.9080200@RedHat.com \
    --to=steved@redhat.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