Linux NFS development
 help / color / mirror / Atom feed
From: Peter Staubach <staubach@redhat.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: Neil Brown <neilb@suse.de>,
	Andrew Morton <akpm@linux-foundation.org>,
	NFS List <nfs@lists.sourceforge.net>
Subject: Re: [PATCH] 64 bit ino support for NFS server
Date: Fri, 17 Aug 2007 14:30:31 -0400	[thread overview]
Message-ID: <46C5E947.4090903@redhat.com> (raw)
In-Reply-To: <20070817165122.GC28529@fieldses.org>

J. Bruce Fields wrote:
> On Thu, Aug 16, 2007 at 12:10:07PM -0400, Peter Staubach wrote:
>   
>> Attached is a new patch which should address the issues raised
>> by Bruce.
>>     
>
> Thanks!
>
>   
>> I also haven't come to any conclusions regarding the value of
>> lease_get_mtime() and whether it should or should not be invoked
>> by fill_post_wcc() too.  I chose not to change this because I
>> thought that it was safer to leave well enough alone.  If we
>> decide to make a change, it can be done separately.
>>     
>
> OK.
>
> Only superficial complaints:
> 	- There were some minor whitespace oddities; running the patch
> 	  through scripts/checkpatch.pl may be the quickest way to catch
> 	  those.
>   

Ugg.  How did those get in there?  :-)

Thanx for pointing this out.  I will ensure that I run checkpatch
before submitting future patches.

> 	- This would be better as two, maybe three separate patches;
> 	  e.g.  moving the lease_get_mtime out of encode_fattr3 could be
> 	  done separately first.  Ideally we'd do some trivial
> 	  transformations like that, followed by one change that
> 	  actually changes the inode behavior.  That makes the whole
> 	  thing trival to review.
>
>   

My test system isn't at a place where I could factor the patch and
do testing.  For the time being, I'd prefer to stick with the single
patch, since it is tested.
> I fixed up the first and added the result to
>
> 	git://linux-nfs.org/~bfields/linux.git for-mm
>
> so it should show up in the next -mm.  I'd happily replace it by a more
> finely split up version if that was something you could whip up in a few
> minutes.

Thanx, Bruce!

       ps

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  reply	other threads:[~2007-08-17 18:37 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-03 19:11 [PATCH] 64 bit ino support for NFS server Peter Staubach
2007-08-03 19:29 ` Peter Staubach
2007-08-04 22:32   ` J. Bruce Fields
2007-08-06 15:40     ` Peter Staubach
2007-08-06 16:09       ` J. Bruce Fields
2007-08-08 20:07     ` Peter Staubach
2007-08-08 20:35       ` J. Bruce Fields
2007-08-08 20:49         ` Peter Staubach
2007-08-08 21:01           ` J. Bruce Fields
2007-08-16 16:10     ` Peter Staubach
2007-08-17 16:51       ` J. Bruce Fields
2007-08-17 18:30         ` Peter Staubach [this message]
2007-08-17 18:36           ` J. Bruce Fields

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=46C5E947.4090903@redhat.com \
    --to=staubach@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=bfields@fieldses.org \
    --cc=neilb@suse.de \
    --cc=nfs@lists.sourceforge.net \
    /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