From: "Zhang, Yanmin" <yanmin.zhang@intel.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
"Luck, Tony" <tony.luck@intel.com>
Cc: "linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Liu, ShuoX" <shuox.liu@intel.com>
Subject: RE: linux-next: build failure after merge of the ia64 tree
Date: Mon, 31 Mar 2014 01:21:48 +0000 [thread overview]
Message-ID: <144086DDB7BB6D429C79280EB1C804D40A79EB0C@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <20140331110756.c4f9b2e9f9f4874e0d90da11@canb.auug.org.au>
Sorry. We would fix it ASAP.
Yanmin
-----Original Message-----
From: Stephen Rothwell [mailto:sfr@canb.auug.org.au]
Sent: Monday, March 31, 2014 8:08 AM
To: Luck, Tony
Cc: linux-next@vger.kernel.org; linux-kernel@vger.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@canb.auug.org.au
next prev parent reply other threads:[~2014-03-31 1:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-31 0:07 Stephen Rothwell
2014-03-31 1:21 ` Zhang, Yanmin [this message]
2014-03-31 6:27 ` [PATCH v2 1/3] pstore: restructure ramoops to support more trace Liu ShuoX
2014-03-31 6:30 ` [PATCH v2 2/3] pstore: add seq_ops for norm zone Liu ShuoX
2014-03-31 6:32 ` [PATCH v2 3/3] pstore: support current records dump in ramoops Liu ShuoX
-- strict thread matches above, loose matches on Subject: below --
2013-01-10 23:54 linux-next: build failure after merge of the ia64 tree Stephen Rothwell
2013-01-10 23:58 ` Seiji Aguchi
2013-01-11 18:44 ` Tony Luck
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=144086DDB7BB6D429C79280EB1C804D40A79EB0C@SHSMSX104.ccr.corp.intel.com \
--to=yanmin.zhang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=shuox.liu@intel.com \
--cc=tony.luck@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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
all inboxes | Powered by JetHome®