RE: linux-next: build failure after merge of the ia64 tree

2014-03-30 Thread Zhang, Yanmin
after merge of the ia64 tree Hi all, After merging the ia64 tree, today's linux-next build (x86_64 allmodconfig) failed like this: fs/built-in.o: In function `pstore_file_open': inode.c:(.text+0xa29e9): undefined reference to `persistent_ram_size' Caused by commit f5d7e81eda59 (&

linux-next: build failure after merge of the ia64 tree

2014-03-30 Thread Stephen Rothwell
Hi all, After merging the ia64 tree, today's linux-next build (x86_64 allmodconfig) failed like this: fs/built-in.o: In function `pstore_file_open': inode.c:(.text+0xa29e9): undefined reference to `persistent_ram_size' Caused by commit f5d7e81eda59 ("pstore: Support current records dump in ramo

Re: linux-next: build failure after merge of the ia64 tree

2013-01-11 Thread Tony Luck
On Thu, Jan 10, 2013 at 3:54 PM, Stephen Rothwell wrote: > ERROR: "pstore_cannot_block_path" [drivers/firmware/efivars.ko] undefined! Should be fixed today (allmodconfig builds for me). I applied Seiji's new version of the patchset that included the missing EXPORT_SYMBOL_GPL. -Tony -- To unsubs

RE: linux-next: build failure after merge of the ia64 tree

2013-01-10 Thread Seiji Aguchi
ubject: linux-next: build failure after merge of the ia64 tree > > Hi all, > > After merging the ia64 tree, today's linux-next build (x86_64_allmodconfig) > failed like this: > > ERROR: "pstore_cannot_block_path" [drivers/firmware/efivars.ko] undefined! > >

linux-next: build failure after merge of the ia64 tree

2013-01-10 Thread Stephen Rothwell
Hi all, After merging the ia64 tree, today's linux-next build (x86_64_allmodconfig) failed like this: ERROR: "pstore_cannot_block_path" [drivers/firmware/efivars.ko] undefined! Caused by commit 1a1df768ea4e ("efi_pstore: Avoid deadlock in non-blocking paths"). I have used the ia64 tree from nex