From: David Howells <dhowells@redhat.com>
To: Linux filesystem caching discussion list <linux-cachefs@redhat.com>
Cc: Trond Myklebust <trond.myklebust@fys.uio.no>,
Andrew Morton <akpm@osdl.org>,
linux-fsdevel@vger.kernel.org
Subject: Re: [Linux-cachefs] Re: [PATCH][RFC] NFS: Adding hooks to enable the use of FS-Cache
Date: Fri, 21 Apr 2006 16:44:43 +0100 [thread overview]
Message-ID: <10977.1145634283@warthog.cambridge.redhat.com> (raw)
In-Reply-To: <4448FD65.7060007@RedHat.com>
Steve Dickson <SteveD@redhat.com> wrote:
> > Hmm... Are you sure that is based on the latest trees?
> Just this morning I did an git fetch on my cloned nfs-2.6
> tree... and everything seem to apply just fine...
Well... if Steve's using my NFS patch, then it overrides the usage of
PG_private to deal with truncate madness. This also needs fixing.
David
prev parent reply other threads:[~2006-04-21 15:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-21 15:14 [PATCH][RFC] NFS: Adding hooks to enable the use of FS-Cache Steve Dickson
2006-04-21 15:31 ` Trond Myklebust
2006-04-21 15:42 ` Steve Dickson
2006-04-21 15:53 ` Trond Myklebust
2006-04-21 15:56 ` Steve Dickson
2006-04-21 15:44 ` David Howells [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=10977.1145634283@warthog.cambridge.redhat.com \
--to=dhowells@redhat.com \
--cc=akpm@osdl.org \
--cc=linux-cachefs@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=trond.myklebust@fys.uio.no \
/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;
as well as URLs for NNTP newsgroup(s).