From: Chuck Lever <chuck.lever@oracle.com>
To: "J. Bruce Fields" <bfields@citi.umich.edu>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH 2/7] nfsd4: edit comment for concision
Date: Wed, 03 Mar 2010 13:06:31 -0500 [thread overview]
Message-ID: <4B8EA527.5060502@oracle.com> (raw)
In-Reply-To: <1267571573-11844-3-git-send-email-bfields@citi.umich.edu>
On 03/02/2010 06:12 PM, J. Bruce Fields wrote:
> Also note units are seconds.
I'd prefer the major edits in this patch be done at the same time you
trim the other documenting comments for the /proc/fs/nfsd API.
> Signed-off-by: J. Bruce Fields<bfields@citi.umich.edu>
> ---
> fs/nfsd/nfsctl.c | 21 ++++++---------------
> 1 files changed, 6 insertions(+), 15 deletions(-)
>
> diff --git a/fs/nfsd/nfsctl.c b/fs/nfsd/nfsctl.c
> index 8bff674..f1ee549 100644
> --- a/fs/nfsd/nfsctl.c
> +++ b/fs/nfsd/nfsctl.c
> @@ -1228,23 +1228,14 @@ static ssize_t __write_leasetime(struct file *file, char *buf, size_t size)
> /**
> * write_leasetime - Set or report the current NFSv4 lease time
> *
> - * Input:
> - * buf: ignored
> - * size: zero
> + * If given a nonzero size, sets the NFSv4 lease time to a number of
> + * seconds (interpreting buf as a C string containing an ascii
> + * representation of the number).
> *
> - * OR
> + * Returns the resulting lease time (as an ascii representation in a
> + * '\n'-terminated C string) in buf.
> *
> - * Input:
> - * buf: C string containing an unsigned
> - * integer value representing the new
> - * NFSv4 lease expiry time
> - * size: non-zero length of C string in @buf
> - * Output:
> - * On success: passed-in buffer filled with '\n'-terminated C
> - * string containing unsigned integer value of the
> - * current lease expiry time;
> - * return code is the size in bytes of the string
> - * On error: return code is zero or a negative errno value
> + * Given a zero size, just returns the lease time in buf.
> */
> static ssize_t write_leasetime(struct file *file, char *buf, size_t size)
> {
--
chuck[dot]lever[at]oracle[dot]com
next prev parent reply other threads:[~2010-03-03 18:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-02 23:12 grace period setting J. Bruce Fields
2010-03-02 23:12 ` [PATCH 1/7] nfsd4: simplify references to nfsd4 lease time J. Bruce Fields
2010-03-02 23:12 ` [PATCH 2/7] nfsd4: edit comment for concision J. Bruce Fields
2010-03-02 23:12 ` [PATCH 3/7] nfsd4: simplify lease/grace interaction J. Bruce Fields
2010-03-02 23:12 ` [PATCH 4/7] nfsd4: remove unnecessary lease-setting function J. Bruce Fields
2010-03-02 23:12 ` [PATCH 5/7] nfsd4: reshuffle lease-setting code to allow reuse J. Bruce Fields
2010-03-02 23:12 ` [PATCH 6/7] nfsd4: allow setting grace period time J. Bruce Fields
2010-03-02 23:12 ` [PATCH 7/7] nfsd4: document lease/grace-period limits J. Bruce Fields
2010-03-03 15:47 ` [PATCH 5/7] nfsd4: reshuffle lease-setting code to allow reuse Peter Staubach
2010-03-06 18:31 ` J. Bruce Fields
2010-03-03 18:06 ` Chuck Lever [this message]
2010-03-06 18:50 ` [PATCH 2/7] nfsd4: edit comment for concision J. Bruce Fields
2010-03-08 15:31 ` Chuck Lever
2010-03-08 18:10 ` J. Bruce Fields
2010-03-08 18:16 ` 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=4B8EA527.5060502@oracle.com \
--to=chuck.lever@oracle.com \
--cc=bfields@citi.umich.edu \
--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