From: Anna Schumaker <Anna.Schumaker@netapp.com>
To: Christoph Hellwig <hch@infradead.org>,
Anna Schumaker <Anna.Schumaker@netapp.com>
Cc: <Trond.Myklebust@primarydata.com>, <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH] NFS: Add v4.2 SEEK support
Date: Wed, 27 Aug 2014 13:54:09 -0400 [thread overview]
Message-ID: <53FE1B41.50307@Netapp.com> (raw)
In-Reply-To: <20140827174325.GB13128@infradead.org>
On 08/27/2014 01:43 PM, Christoph Hellwig wrote:
> On Wed, Aug 27, 2014 at 11:18:49AM -0400, Anna Schumaker wrote:
>> This patch adds support for the NFS v4.2 operation SEEK.
>>
>> I think nfs4proc.c and nfs4xdr.c have grown out of control, and I would like
>> to avoid adding new functions to these files unless absolutely necessary.
>> Therefore, I created nfs4.2proc.c and nfs4.2xdr.h in an attempt to separate
>> out the new code.
>>
>> Questions? Comments? Thoughts?
> I hate the dot in the name :) why not nfs42proc.c and co?
Sure, I can change that. I put the dot because I kept reading it "fourty-two" and now "four two".
>
> Also without splitting out the much larger 4.1 ops this seems a bit
> pointless, although I generally like the idea.
Oh, but I want to split those out too :D. I figured it would be easiest to come up with a solution now, when we're adding a new minor version, and then split out v4.1 once we know what we're doing.
Anna
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2014-08-27 17:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-27 15:18 [PATCH] NFS: Add v4.2 SEEK support Anna Schumaker
2014-08-27 15:18 ` [PATCH] NFS: Implement SEEK Anna Schumaker
2014-08-27 17:40 ` [PATCH] NFS: Add v4.2 SEEK support Marc Eshel
2014-08-27 17:51 ` Anna Schumaker
2014-08-27 17:43 ` Christoph Hellwig
2014-08-27 17:54 ` Anna Schumaker [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=53FE1B41.50307@Netapp.com \
--to=anna.schumaker@netapp.com \
--cc=Trond.Myklebust@primarydata.com \
--cc=hch@infradead.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.