mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dave Hansen <haveblue@us.ibm.com>
To: linux-kernel@vger.kernel.org
Cc: dhowells@redhat.com, trond.myklebust@fys.uio.no,
	Andrew Morton <akpm@osdl.org>
Subject: Re: + fs-cache-make-kafs-use-fs-cache.patch added to -mm tree
Date: Tue, 08 Aug 2006 10:30:06 -0700	[thread overview]
Message-ID: <1155058206.19249.93.camel@localhost.localdomain> (raw)
In-Reply-To: <200608050009.k7509mMx019642@shell0.pdx.osdl.net>

On Fri, 2006-08-04 at 17:09 -0700, akpm@osdl.org wrote:
> The attached patch makes the kAFS filesystem in fs/afs/ use FS-Cache, and
> through it any attached caches.  The kAFS filesystem will use caching
> automatically if it's available.

I get the following warning when compiling AFS, but leaving FSCACHE
compiled out in 2.6.18-rc3-mm2:

fs/afs/vnode.c:522: warning: 'afs_vnode_cache_now_uncached' defined but not used

The attached patch fixes it.

Signed-off-by: Dave Hansen <haveblue@us.ibm.com>

 lxc-dave/fs/afs/vnode.c |    2 +-
 1 files changed, 1 insertion(+), 1 deletion(-)

diff -puN fs/afs/vnode.c~fcache-exports fs/afs/vnode.c
--- lxc/fs/afs/vnode.c~fcache-exports	2006-08-08 10:21:53.000000000 -0700
+++ lxc-dave/fs/afs/vnode.c	2006-08-08 10:22:53.000000000 -0700
@@ -508,7 +508,6 @@ static void afs_vnode_cache_mark_pages_c
 	}
 
 } /* end afs_vnode_cache_mark_pages_cached() */
-#endif
 
 /*****************************************************************************/
 /*
@@ -552,3 +551,4 @@ static void afs_vnode_cache_now_uncached
 	_leave("");
 
 } /* end afs_vnode_cache_now_uncached() */
+#endif
_


-- Dave


       reply	other threads:[~2006-08-08 17:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200608050009.k7509mMx019642@shell0.pdx.osdl.net>
2006-08-08 17:30 ` Dave Hansen [this message]
2006-08-08 17:42 ` David Howells

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=1155058206.19249.93.camel@localhost.localdomain \
    --to=haveblue@us.ibm.com \
    --cc=akpm@osdl.org \
    --cc=dhowells@redhat.com \
    --cc=linux-kernel@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

Powered by JetHome