Re: linux-next: build failure after merge of the akpm tree
From: Peng Tao
Date: Fri Jun 07 2013 - 03:27:23 EST
On Fri, Jun 7, 2013 at 2:28 PM, Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx> wrote:
> Hi Andrew,
> After merging the akpm tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
> In file included from drivers/staging/lustre/include/linux/libcfs/linux/libcfs.h:49:0,
> from drivers/staging/lustre/include/linux/libcfs/libcfs.h:44,
> from drivers/staging/lustre/include/linux/lnet/linux/lib-lnet.h:45,
> from drivers/staging/lustre/include/linux/lnet/lib-lnet.h:44,
> from drivers/staging/lustre/lnet/lnet/api-ni.c:38:
> drivers/staging/lustre/include/linux/libcfs/linux/linux-mem.h: In function 'set_shrinker':
> drivers/staging/lustre/include/linux/libcfs/linux/linux-mem.h:102:3: error: 'struct shrinker' has no member named 'shrink'
> s->shrink = func;
> Caused by commit a37f14f05f2f ("shrinker: Kill old ->shrink API") from
> the akpm tree interacting with the new Lustre client code from the
> staging tree.
> I have just disabled the Lustre client code again (by reverting commit
> ee04fd11f11f ("Revert "Revert "staging/lustre: drop CONFIG_BROKEN
> dependency""")) and maybe someone can tell me what I need to do to fix
> this when I get back in a week.
I have a patchset to fix this but haven't yet sent out because it will
break build in Greg's staging tree. I can send it now but please tell
me to whom I should send the patches? Greg's tree doesn't contain
shrinker change, and mm- tree doesn't have Lustre code.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/