linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steve Dickson <SteveD@redhat.com>
To: Benny Halevy <bhalevy@panasas.com>
Cc: NFS list <linux-nfs@vger.kernel.org>,
	pNFS Mailing List <pnfs@linux-nfs.org>
Subject: Re: [PATCH 0/2] nfs-utils: nfsstat fix for 2.6.33
Date: Mon, 08 Feb 2010 10:38:18 -0500	[thread overview]
Message-ID: <4B702FEA.8070905@RedHat.com> (raw)
In-Reply-To: <4B3B6981.8030807@panasas.com>



On 12/30/2009 09:53 AM, Benny Halevy wrote:
> Steve,
> 
> The first patch in this series adds reclaim_complete to the client stats.
> The second one cleans up the array size definitions for nfs ops.
> 
> [PATCH 1/2] nfsstat: update cltproc4info for 2.6.33
> [PATCH 2/2] nfsstat: use symbolic constants for operation array sizes
> 
Committed...

steved.

      parent reply	other threads:[~2010-02-08 15:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-30 14:53 [PATCH 0/2] nfs-utils: nfsstat fix for 2.6.33 Benny Halevy
2009-12-30 14:55 ` [PATCH 1/2] nfsstat: update cltproc4info " Benny Halevy
2009-12-30 14:55 ` [PATCH 2/2] nfsstat: use symbolic constants for operation array sizes Benny Halevy
2010-02-08 15:38 ` 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=4B702FEA.8070905@RedHat.com \
    --to=steved@redhat.com \
    --cc=bhalevy@panasas.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=pnfs@linux-nfs.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;
as well as URLs for NNTP newsgroup(s).