From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org, Hugh Dickens <hugh@veritas.com>,
"H. Peter Anvin" <hpa@zytor.com>,
Alan Jenkins <alan-jenkins@tuffmail.co.uk>,
Rafa? Mi?ecki <zajec5@gmail.com>
Subject: [PATCH 5/3] x86: fix compile error with corruption checking disabled
Date: Sun, 07 Sep 2008 14:54:41 -0700 [thread overview]
Message-ID: <48C44DA1.8060402@goop.org> (raw)
In-Reply-To: <20080907155115.GA28495@elte.hu>
Fix compile error:
arch/x86/mm/init_32.c: In function 'mem_init':
arch/x86/mm/init_32.c:908: error: implicit declaration of function 'start_periodic_check_for_corruption'
Signed-off-by: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
---
include/linux/kernel.h | 4 ++++
1 file changed, 4 insertions(+)
===================================================================
--- a/include/linux/kernel.h
+++ b/include/linux/kernel.h
@@ -257,6 +257,10 @@
static inline void check_for_bios_corruption(void)
{
}
+
+static inline void start_periodic_check_for_corruption(void)
+{
+}
#endif
/* Values used for system_state */
next prev parent reply other threads:[~2008-09-07 21:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <patchbomb.1220777491@localhost>
[not found] ` <72081a970effa1a32861.1220777494@localhost>
2008-09-07 9:11 ` [PATCH 3 of 3] x86: clean up memory corruption check and add more kernel parameters Ingo Molnar
2008-09-07 9:37 ` [PATCH 4/3] x86: default corruption check to off, but put parameter default in Kconfig Jeremy Fitzhardinge
2008-09-07 15:40 ` Ingo Molnar
[not found] ` <20080907155030.GA24741@elte.hu>
2008-09-07 15:51 ` Ingo Molnar
2008-09-07 21:54 ` Jeremy Fitzhardinge [this message]
2008-09-08 18:03 ` [PATCH 5/3] x86: fix compile error with corruption checking disabled Ingo Molnar
2008-09-07 15:24 ` [PATCH 0 of 3] Low memory corruption detection and workaround Alan Jenkins
2008-09-08 11:23 ` Nick Piggin
2008-09-08 16:47 ` Jeremy Fitzhardinge
2008-09-08 17:01 ` Alan Cox
2008-09-08 18:44 ` Nick Piggin
2008-09-08 10:52 ` Hugh Dickins
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=48C44DA1.8060402@goop.org \
--to=jeremy@goop.org \
--cc=alan-jenkins@tuffmail.co.uk \
--cc=hpa@zytor.com \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=zajec5@gmail.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