From: Jim Rees <rees@umich.edu>
To: Bryan Schumaker <bjschuma@netapp.com>
Cc: "Myklebust, Trond" <Trond.Myklebust@netapp.com>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH 1/5] NFS: call_sync function
Date: Wed, 22 Dec 2010 18:54:48 -0500 [thread overview]
Message-ID: <20101222235447.GA25778@merit.edu> (raw)
In-Reply-To: <4D1272B6.9000907@netapp.com>
Bryan Schumaker wrote:
This patch changes nfs4_call_sync() from a macro into a
static inline function.
Makes sense, but why change the arguments?
next prev parent reply other threads:[~2010-12-22 23:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-22 21:50 [PATCH 1/5] NFS: call_sync function Bryan Schumaker
2010-12-22 23:54 ` Jim Rees [this message]
2010-12-23 0:14 ` Trond Myklebust
2010-12-23 0:18 ` Chuck Lever
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=20101222235447.GA25778@merit.edu \
--to=rees@umich.edu \
--cc=Trond.Myklebust@netapp.com \
--cc=bjschuma@netapp.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