[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <144086DDB7BB6D429C79280EB1C804D40A79EB0C@SHSMSX104.ccr.corp.intel.com>
Date: Mon, 31 Mar 2014 01:21:48 +0000
From: "Zhang, Yanmin" <yanmin.zhang@...el.com>
To: Stephen Rothwell <sfr@...b.auug.org.au>,
"Luck, Tony" <tony.luck@...el.com>
CC: "linux-next@...r.kernel.org" <linux-next@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"Liu, ShuoX" <shuox.liu@...el.com>
Subject: RE: linux-next: build failure after merge of the ia64 tree
Sorry. We would fix it ASAP.
Yanmin
-----Original Message-----
From: Stephen Rothwell [mailto:sfr@...b.auug.org.au]
Sent: Monday, March 31, 2014 8:08 AM
To: Luck, Tony
Cc: linux-next@...r.kernel.org; linux-kernel@...r.kernel.org; Liu, ShuoX; Zhang, Yanmin
Subject: 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:
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 ramoops").
I have used the ia64 tree from next-20140328 for today.
--
Cheers,
Stephen Rothwell sfr@...b.auug.org.au
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists