From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Fabio Olive Leite <fleite@redhat.com>
Cc: linux-nfs <nfs@lists.sourceforge.net>
Subject: Re: [PATCH] Attribute timeout handling and wrapping u32 jiffies
Date: Tue, 31 Jul 2007 15:47:33 -0400 [thread overview]
Message-ID: <1185911253.6700.52.camel@localhost> (raw)
In-Reply-To: <20070731162503.GC2964@sleipnir.redhat.com>
On Tue, 2007-07-31 at 13:25 -0300, Fabio Olive Leite wrote:
> Hi Trond,
>
> On Thu, Jul 26, 2007 at 10:59:00PM -0300, Fabio Olive Leite wrote:
> >
> > Tried it out and it behaves correctly. Thanks for your suggestions.
> > The patch below is the final version, and fixes the attribute
> > timeout issue with wrapping jiffies.
> >
> > ...
>
> Have you had a chance to review/commit this patch? Should I do any
> more testing on it?
It looked good when I laster reviewed it, but I haven't yet tested it
myself. Please send me a reminder if you don't see it appear in the next
NFS_ALL release (which should be within a week).
Cheers
Trond
-------------------------------------------------------------------------
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
next prev parent reply other threads:[~2007-07-31 19:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-25 3:08 [PATCH] Attribute timeout handling and wrapping u32 jiffies Fabio Olive Leite
2007-07-25 14:00 ` Trond Myklebust
2007-07-25 14:28 ` Fabio Olive Leite
2007-07-25 14:32 ` Trond Myklebust
2007-07-25 14:54 ` Fabio Olive Leite
2007-07-27 1:59 ` Fabio Olive Leite
2007-07-31 16:25 ` Fabio Olive Leite
2007-07-31 19:47 ` Trond Myklebust [this message]
2007-08-22 18:25 ` Fabio Olive Leite
2007-08-22 18:47 ` J. Bruce Fields
2007-08-27 13:23 ` Trond Myklebust
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=1185911253.6700.52.camel@localhost \
--to=trond.myklebust@fys.uio.no \
--cc=fleite@redhat.com \
--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 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.