From: "Emilio Jesús Gallego Arias" <egallego@telefonica.net>
To: agoddard@purdue.edu
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH] Build Broken for 2.6.0-test3-bk8
Date: Wed, 20 Aug 2003 22:22:32 +0200 [thread overview]
Message-ID: <1061410952.568.8.camel@ellugar> (raw)
I got the same error, and applied this patch. Don't know if it's the way
to go:
# This is a BitKeeper generated patch for the following project:
# Project Name: Linux kernel tree
# This patch format is intended for GNU patch command version 2.5 or
higher.
# This patch includes the following deltas:
# ChangeSet 1.1279 -> 1.1280
# arch/i386/kernel/setup.c 1.92 -> 1.93
# arch/i386/kernel/acpi/boot.c 1.27 -> 1.28
#
# The following is the BitKeeper ChangeSet Log
# --------------------------------------------
# 03/08/20 emilio@ellugar.(none) 1.1280
# - Fix build error due a missing include.
# --------------------------------------------
#
diff -Nru a/arch/i386/kernel/acpi/boot.c b/arch/i386/kernel/acpi/boot.c
--- a/arch/i386/kernel/acpi/boot.c Wed Aug 20 22:18:04 2003
+++ b/arch/i386/kernel/acpi/boot.c Wed Aug 20 22:18:04 2003
@@ -34,6 +34,7 @@
#if defined (CONFIG_X86_LOCAL_APIC)
#include <mach_apic.h>
#include <mach_mpparse.h>
+#include <asm/io_apic.h>
#endif
#define PREFIX "ACPI: "
diff -Nru a/arch/i386/kernel/setup.c b/arch/i386/kernel/setup.c
--- a/arch/i386/kernel/setup.c Wed Aug 20 22:18:04 2003
+++ b/arch/i386/kernel/setup.c Wed Aug 20 22:18:04 2003
@@ -43,6 +43,7 @@
#include <asm/setup.h>
#include <asm/arch_hooks.h>
#include <asm/sections.h>
+#include <asm/io_apic.h>
#include "setup_arch_pre.h"
#include "mach_resources.h"
next reply other threads:[~2003-08-20 20:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-20 20:22 Emilio Jesús Gallego Arias [this message]
2003-08-20 22:40 ` [PATCH] Build Broken for 2.6.0-test3-bk8 Alex Goddard
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=1061410952.568.8.camel@ellugar \
--to=egallego@telefonica.net \
--cc=agoddard@purdue.edu \
--cc=linux-kernel@vger.kernel.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