linux-next: build failure after merge of the cifs tree
in [Kernel]
|
Prev: [RFC PATCH 1/2] tracing: Remove sysprof ftrace plugin
Next: v2 Update sysfs node routines for new sysfs memory directories
From: Stephen Rothwell on 15 Jul 2010 20:00 Hi Steve, After merging the cifs tree, today's linux-next build (powerpc ppc64_defconfig) failed like this: In file included from fs/cifs/cifsfs.c:50: fs/cifs/fscache.h:49: error: expected identifier or '(' before '{' token Caused by commit 07be494ba2f46852ec6d1faab8111f5179cc7bb4 ("cifs: define server-level cache index objects and register them"). CONFIG_CIFS_FSCACHE is not defined in this build. I have used the cifs tree from next-20100715 for today. -- Cheers, Stephen Rothwell sfr(a)canb.auug.org.au http://www.canb.auug.org.au/~sfr/
From: Steve French on 16 Jul 2010 00:40
On Thu, Jul 15, 2010 at 6:51 PM, Stephen Rothwell <sfr(a)canb.auug.org.au> wrote: > Hi Steve, > > After merging the cifs tree, today's linux-next build (powerpc > ppc64_defconfig) failed like this: > > In file included from fs/cifs/cifsfs.c:50: > fs/cifs/fscache.h:49: error: expected identifier or '(' before '{' token > > Caused by commit 07be494ba2f46852ec6d1faab8111f5179cc7bb4 ("cifs: define > server-level cache index objects and register them"). > CONFIG_CIFS_FSCACHE is not defined in this build. > > I have used the cifs tree from next-20100715 for today. Thx. I have fixed this in cifs-2.6.git There were three places where Suresh's fscache patch set for cifs forgot ifdefs or misdefined the stub function (when fscache support is turned off). -- Thanks, Steve -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ |