linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Trond Myklebust <Trond.Myklebust@netapp.com>
To: Vasily Averin <vvs@parallels.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCHv2 0/2] minor cleanup of sunrpc/lockd debug
Date: Thu, 02 Jun 2011 10:13:21 -0400	[thread overview]
Message-ID: <1307024001.9634.0.camel@lade.trondhjem.org> (raw)
In-Reply-To: <4DE768B7.8000301@parallels.com>

On Thu, 2011-06-02 at 14:40 +0400, Vasily Averin wrote: 
> few minor cleanup of lockd/sunrpc debug messages
> 
> sunrpc: Use dprint_status() macro in call_decode()
> lockd: properly convert be32 values in debug messages
> 
> v2 changes:
> 1) inline patches
> 2) lockd: properly convert be32 values in debug messages
> 	Using be32_to_cpu() instead ntohl()

Already committed to the nfs-for-next branch of my git tree.

Thanks!
  Trond
-- 
Trond Myklebust
Linux NFS client maintainer

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


      reply	other threads:[~2011-06-02 14:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-02 10:40 [PATCHv2 0/2] minor cleanup of sunrpc/lockd debug Vasily Averin
2011-06-02 14:13 ` Trond Myklebust [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=1307024001.9634.0.camel@lade.trondhjem.org \
    --to=trond.myklebust@netapp.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=vvs@parallels.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;
as well as URLs for NNTP newsgroup(s).