From: Don Zickus <dzickus@redhat.com>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for Dec 7 (x86, not SMP)
Date: Wed, 7 Dec 2011 14:42:52 -0500 [thread overview]
Message-ID: <20111207194252.GH1669@redhat.com> (raw)
In-Reply-To: <4EDFBA25.1020102@xenotime.net>
On Wed, Dec 07, 2011 at 11:10:29AM -0800, Randy Dunlap wrote:
> On 12/06/2011 10:12 PM, Stephen Rothwell wrote:
> > Hi all,
> >
> > Changes since 20111206:
>
>
> When CONFIG_SMP is not enabled:
> (I think that's the cause, but it could be some other kconfig option.)
Yeah it doesn't seem to be that one. I think it is CONFIG_X86_LOCAL_APIC,
but I can't quickly figure out how to disable it (it keeps getting
re-enabled somewhere).
Can you attach your .config?
Thanks,
Don
>
>
> arch/x86/built-in.o: In function `test_nmi_ipi':
> nmi_selftest.c:(.text+0xf7a0): undefined reference to `apic'
>
> --
> ~Randy
> *** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2011-12-07 19:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-07 6:12 linux-next: Tree for Dec 7 Stephen Rothwell
2011-12-07 10:39 ` Sasha Levin
2011-12-07 19:59 ` Sasha Levin
2011-12-07 19:10 ` linux-next: Tree for Dec 7 (x86, not SMP) Randy Dunlap
2011-12-07 19:42 ` Don Zickus [this message]
2011-12-07 20:43 ` Randy Dunlap
2011-12-07 21:06 ` Don Zickus
2011-12-08 2:45 ` Randy Dunlap
2011-12-08 4:35 ` [tip:x86/debug] x86, NMI: NMI selftest depends on the local apic tip-bot for Don Zickus
2011-12-07 20:41 ` linux-next: Tree for Dec 7 (kvm) Randy Dunlap
2011-12-07 20:53 ` linux-next: Tree for Dec 7 (hid/hid-wiimote) Randy Dunlap
2011-12-07 20:33 ` [PATCH] HID: wiimote: Select INPUT_FF_MEMLESS David Herrmann
2011-12-07 21:07 ` simon
2011-12-07 21:07 ` simon
2011-12-08 8:31 ` David Herrmann
2011-12-08 16:23 ` simon
2011-12-08 22:43 ` Sean Young
2011-12-07 21:51 ` Randy Dunlap
2011-12-11 23:27 ` Jiri Kosina
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=20111207194252.GH1669@redhat.com \
--to=dzickus@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=sfr@canb.auug.org.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.