From: Ingo Molnar <mingo@elte.hu>
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>,
Robert Richter <robert.richter@amd.com>,
Andre Przywara <andre.przywara@amd.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH -next] x86: perf_event_amd.c needs <asm/apicdef.h>
Date: Wed, 28 Sep 2011 08:58:02 +0200 [thread overview]
Message-ID: <20110928065801.GA14126@elte.hu> (raw)
In-Reply-To: <4E820138.90301@xenotime.net>
* Randy Dunlap <rdunlap@xenotime.net> wrote:
> From: Randy Dunlap <rdunlap@xenotime.net>
>
> Fix build error by adding <asm/apicdef.h> header file:
>
> arch/x86/kernel/cpu/perf_event_amd.c:350:2: error: 'BAD_APICID' undeclared (first use in this function)
>
> Signed-off-by: Randy Dunlap <rdunlap@xenotime.net>
> ---
>
> Found in linux-next and patch only applies cleanly to linux-next,
> but looks like mainline could use a similar patch (with more
> header files).
>
> arch/x86/kernel/cpu/perf_event_amd.c | 1 +
> 1 file changed, 1 insertion(+)
Applied to tip:perf/core, thanks Randy!
Ingo
next prev parent reply other threads:[~2011-09-28 6:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-26 7:23 linux-next: Tree for Sept 26 Stephen Rothwell
2011-09-26 16:52 ` linux-next: Tree for Sept 26 (xen) Randy Dunlap
2011-09-26 17:18 ` [Xen-devel] " Konrad Rzeszutek Wilk
2011-09-26 17:10 ` linux-next: Tree for Sept 26 (olpc) Randy Dunlap
2011-09-26 17:31 ` linux-next: Tree for Sept 26 (block/mtip32xx) Randy Dunlap
2011-09-27 17:00 ` [PATCH -next] x86: perf_event_amd.c needs <asm/apicdef.h> Randy Dunlap
2011-09-28 6:58 ` Ingo Molnar [this message]
2011-09-27 17:31 ` [PATCH -next] dmar: fix build warnings when ACPI is not enabled Randy Dunlap
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=20110928065801.GA14126@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=andre.przywara@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=robert.richter@amd.com \
--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.