From: Andi Kleen <andi@firstfloor.org>
To: mingo@elte.hu, linux-kernel@vger.kernel.org
Subject: [PATCH] [2/2] Fix warning with !CONFIG_X86_RESERVE_LOW_64K
Date: Mon, 10 Nov 2008 09:09:39 +0100 (CET) [thread overview]
Message-ID: <20081110080939.544E63E660F@basil.firstfloor.org> (raw)
In-Reply-To: <20081110909.153463053@firstfloor.org>
Signed-off-by: Andi Kleen <ak@linux.intel.com>
---
arch/x86/kernel/setup.c | 2 ++
1 file changed, 2 insertions(+)
Index: linux-2.6.28-rc4-test/arch/x86/kernel/setup.c
===================================================================
--- linux-2.6.28-rc4-test.orig/arch/x86/kernel/setup.c 2008-10-24 13:34:40.000000000 +0200
+++ linux-2.6.28-rc4-test/arch/x86/kernel/setup.c 2008-11-10 09:06:00.000000000 +0100
@@ -738,6 +738,7 @@
}
#endif
+#ifdef CONFIG_X86_RESERVE_LOW_64K
static int __init dmi_low_memory_corruption(const struct dmi_system_id *d)
{
printk(KERN_NOTICE
@@ -749,6 +750,7 @@
return 0;
}
+#endif
/* List of systems that have known low memory corruption BIOS problems */
static struct dmi_system_id __initdata bad_bios_dmi_table[] = {
prev parent reply other threads:[~2008-11-10 7:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-10 8:09 [PATCH] [1/2] Move iomap.h into arch/x86/include/asm Andi Kleen
2008-11-10 8:09 ` Andi Kleen [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=20081110080939.544E63E660F@basil.firstfloor.org \
--to=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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