From: Randy Dunlap <randy.dunlap@oracle•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>, dhowells@redhat•com
Cc: linux-next@vger•kernel.org, LKML <linux-kernel@vger•kernel.org>
Subject: Re: linux-next: Tree for December 18 (fscache)
Date: Thu, 18 Dec 2008 09:25:57 -0800 [thread overview]
Message-ID: <20081218092557.b274e9dd.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20081218230637.c879a046.sfr@canb.auug.org.au>
On Thu, 18 Dec 2008 23:06:37 +1100 Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20081217:
>
> New tree:
> fscache
When CONFIG_BLOCK=n:
build-r7417.out:/local/linsrc/linux-next-20081218/fs/cachefiles/cf-interface.c:357: error: implicit declaration of function 'fsync_super'
build-r7417.out:make[3]: *** [fs/cachefiles/cf-interface.o] Error 1
Should include/linux/buffer_head.h have an empty stub for fsync_super()
or does fscache even make sense when CONFIG_BLOCK=n?
---
~Randy
next prev parent reply other threads:[~2008-12-18 17:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-18 12:06 linux-next: Tree for December 18 Stephen Rothwell
2008-12-18 17:21 ` linux-next: Tree for December 18 (slow-work) Randy Dunlap
2008-12-18 17:45 ` David Howells
2008-12-18 17:25 ` Randy Dunlap [this message]
2008-12-18 17:47 ` linux-next: Tree for December 18 (fscache) David Howells
2008-12-18 23:57 ` linux-next: Tree for December 18 (irq.h documentation) Randy Dunlap
2008-12-19 0:33 ` Yinghai Lu
2008-12-19 0:45 ` Randy Dunlap
2008-12-19 0:57 ` Yinghai Lu
2008-12-19 1:00 ` Randy Dunlap
2008-12-19 0:14 ` linux-next: Tree for December 18 (patch: kernel-doc notation) Randy Dunlap
2008-12-19 10:39 ` Dave Chinner
2008-12-22 22:49 ` Andrew Morton
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=20081218092557.b274e9dd.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle$(echo .)com \
--cc=dhowells@redhat$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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