Linux-Next discussions
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
	linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	David Howells <dhowells@redhat.com>
Subject: Re: linux-next: Tree for January 15  (afs/fscache)
Date: Fri, 16 Jan 2009 12:52:07 +1100	[thread overview]
Message-ID: <20090116125207.e1e79798.sfr@canb.auug.org.au> (raw)
In-Reply-To: <496F7DE4.7020600@oracle.com>

[-- Attachment #1: Type: text/plain, Size: 2479 bytes --]

Hi Trond,

On Thu, 15 Jan 2009 10:18:12 -0800 Randy Dunlap <randy.dunlap@oracle.com> wrote:
>
> (still)
> 
> when CONFIG_AFS=y and CONFIG_FSCACHE=m:
> (CONFIG_AFS_FSCACHE=n)
> 
> 
> fs/built-in.o: In function `afs_cell_purge':
> (.text+0x6b13e): undefined reference to `__fscache_relinquish_cookie'
> fs/built-in.o: In function `afs_releasepage':
> file.c:(.text+0x6fd4d): undefined reference to `__fscache_uncache_page'
> fs/built-in.o: In function `afs_readpages':
> file.c:(.text+0x7022b): undefined reference to `__fscache_read_or_alloc_pages'
> fs/built-in.o: In function `afs_readpage':
> file.c:(.text+0x7063b): undefined reference to `__fscache_read_or_alloc_page'
> file.c:(.text+0x707c0): undefined reference to `__fscache_uncache_page'
> file.c:(.text+0x7083a): undefined reference to `__fscache_write_page'
> file.c:(.text+0x7086d): undefined reference to `__fscache_uncache_page'
> fs/built-in.o: In function `afs_invalidatepage':
> file.c:(.text+0x70ab3): undefined reference to `__fscache_uncache_page'
> fs/built-in.o: In function `afs_clear_inode':
> (.text+0x778be): undefined reference to `__fscache_relinquish_cookie'
> fs/built-in.o: In function `afs_iget':
> (.text+0x77cad): undefined reference to `__fscache_acquire_cookie'
> fs/built-in.o: In function `afs_iget':
> (.text+0x77e25): undefined reference to `__fscache_attr_changed'
> fs/built-in.o: In function `afs_iget':
> (.text+0x77ff6): undefined reference to `__fscache_relinquish_cookie'
> fs/built-in.o: In function `afs_vlocation_apply_update':
> vlocation.c:(.text+0x81989): undefined reference to `__fscache_update_cookie'
> fs/built-in.o: In function `afs_vlocation_lookup':
> (.text+0x822f0): undefined reference to `__fscache_acquire_cookie'
> fs/built-in.o: In function `afs_vlocation_lookup':
> (.text+0x8269c): undefined reference to `__fscache_update_cookie'
> fs/built-in.o: In function `afs_vlocation_reaper':
> vlocation.c:(.text+0x82f01): undefined reference to `__fscache_relinquish_cookie'
> fs/built-in.o: In function `afs_put_volume':
> (.text+0x86b95): undefined reference to `__fscache_relinquish_cookie'
> fs/built-in.o: In function `afs_volume_lookup':
> (.text+0x8784e): undefined reference to `__fscache_acquire_cookie'

I have dropped the nfs tree form linux-next for today (there was an ia64
build problem as well).

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

      reply	other threads:[~2009-01-16  1:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-15  6:04 linux-next: Tree for January 15 Stephen Rothwell
2009-01-15 10:35 ` [BUILD_FAILURE] next-20090115 - s390x - mm/kmemleak.c Kamalesh Babulal
2009-01-15 11:20   ` Heiko Carstens
2009-01-15 11:55     ` Catalin Marinas
2009-01-15 12:05       ` Heiko Carstens
2009-01-15 17:00         ` Catalin Marinas
2009-01-15 12:08       ` Pekka Enberg
2009-01-15 12:13         ` Heiko Carstens
2009-01-15 12:16           ` Catalin Marinas
2009-01-15 12:13         ` Catalin Marinas
2009-01-15 18:18 ` linux-next: Tree for January 15 (afs/fscache) Randy Dunlap
2009-01-16  1:52   ` Stephen Rothwell [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=20090116125207.e1e79798.sfr@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=dhowells@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=randy.dunlap@oracle.com \
    --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