From: Randy Dunlap <rdunlap@xenotime.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Linus <torvalds@linux-foundation.org>,
bluesmoke-devel@lists.sourceforge.net,
Mauro Carvalho Chehab <mchehab@redhat.com>
Subject: Re: linux-next: Tree for Oct 25 (sb_edac.c)
Date: Wed, 26 Oct 2011 11:47:34 -0700 [thread overview]
Message-ID: <4EA855C6.806@xenotime.net> (raw)
In-Reply-To: <20111025203628.40a1b8a475e32053aa34dabe@canb.auug.org.au>
On 10/25/11 02:36, Stephen Rothwell wrote:
> Hi all,
sb_edac.c:(.text.unlikely+0x8370): undefined reference to `x86_mce_decoder_chain'
sb_edac.c:(.text.unlikely+0x87aa): undefined reference to `x86_mce_decoder_chain'
when CONFIG_X86_MCE is not enabled.
--
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
prev parent reply other threads:[~2011-10-26 18:47 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-25 9:36 linux-next: Tree for Oct 25 Stephen Rothwell
2011-10-25 9:43 ` Stephen Rothwell
2011-10-25 10:42 ` Stephen Rothwell
2011-10-26 0:34 ` linux-next: Tree for Oct 25 (agp/intel-gtt.c) Randy Dunlap
2011-11-03 21:21 ` Randy Dunlap
2011-10-26 0:42 ` linux-next: Tree for Oct 25 (crypto) Randy Dunlap
2011-10-26 6:27 ` Herbert Xu
2011-10-26 12:33 ` Stefan Richter
2011-10-26 16:27 ` Randy Dunlap
2011-10-26 17:15 ` Stefan Richter
2011-10-27 7:05 ` Valdis.Kletnieks
2011-10-27 7:45 ` Herbert Xu
2011-10-29 23:20 ` Valdis.Kletnieks
2011-10-26 18:26 ` linux-next: Tree for Oct 25 (mfd/ab8500) Randy Dunlap
2011-10-30 23:04 ` Samuel Ortiz
2011-10-26 18:37 ` linux-next: Tree for Oct 25 (pci/ats.c) Randy Dunlap
2011-11-10 13:09 ` Ingo Molnar
2011-10-26 18:39 ` linux-next: Tree for Oct 25 (target) Randy Dunlap
2011-10-26 19:53 ` Nicholas A. Bellinger
2011-10-26 20:40 ` Stephen Rothwell
2011-10-26 20:42 ` Nicholas A. Bellinger
2011-10-26 18:47 ` Randy Dunlap [this message]
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=4EA855C6.806@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=bluesmoke-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mchehab@redhat.com \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@linux-foundation.org \
/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;
as well as URLs for NNTP newsgroup(s).