From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Linus Torvalds <torvalds@osdl.org>
Cc: linux-kernel@vger.kernel.org, matt_domsch@dell.com, akpm <akpm@osdl.org>
Subject: [PATCH] edd (Re: Linux 2.6.8-rc1)
Date: Sun, 11 Jul 2004 16:00:19 -0700 [thread overview]
Message-ID: <20040711160019.00c2d658.rddunlap@osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0407111120010.1764@ppc970.osdl.org>
| Matt Domsch:
| o EDD: store mbr_signature on first 16 int13 devices
| o EDD: x86-64 build fix
|
drivers/built-in.o: In function `edd_has_mbr_signature':
drivers/built-in.o(.text+0x13b84f): undefined reference to `edd'
drivers/built-in.o: In function `edd_has_edd_info':
drivers/built-in.o(.text+0x13b871): undefined reference to `edd'
drivers/built-in.o: In function `edd_device_register':
drivers/built-in.o(.text+0x13c7ab): undefined reference to `edd'
drivers/built-in.o(.text+0x13c7c3): undefined reference to `edd'
drivers/built-in.o: In function `edd_init':
drivers/built-in.o(.init.text+0xd395): undefined reference to `edd'
drivers/built-in.o(.init.text+0xd39c): more undefined references to `edd' follow
make: *** [.tmp_vmlinux1] Error 1
CONFIG_EDD=y on X86o
'edd' needs to be exported for drivers/firmware/edd.c
diffstat:=
arch/i386/kernel/setup.c | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff -Naurp ./arch/i386/kernel/setup.c~edd_reference ./arch/i386/kernel/setup.c
--- ./arch/i386/kernel/setup.c~edd_reference 2004-07-11 15:47:27.000000000 -0700
+++ ./arch/i386/kernel/setup.c 2004-07-11 15:42:05.000000000 -0700
@@ -628,10 +628,10 @@ static int __init copy_e820_map(struct e
}
#if defined(CONFIG_EDD) || defined(CONFIG_EDD_MODULE)
+
struct edd edd;
-#ifdef CONFIG_EDD_MODULE
EXPORT_SYMBOL(edd);
-#endif
+
/**
* copy_edd() - Copy the BIOS EDD information
* from boot_params into a safe place.
next prev parent reply other threads:[~2004-07-11 23:07 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-11 18:29 Linux 2.6.8-rc1 Linus Torvalds
2004-07-11 23:00 ` Randy.Dunlap [this message]
2004-07-12 3:02 ` [PATCH] edd (Re: Linux 2.6.8-rc1) Adrian Bunk
2004-07-12 4:49 ` Matt Domsch
2004-07-12 5:21 ` Randy.Dunlap
2004-07-12 9:26 ` Linux 2.6.8-rc1 Matthias Andree
2004-07-12 18:54 ` Martin Schlemmer
2004-07-12 9:34 ` Paolo Ciarrocchi
2004-07-12 15:42 ` Adrian Bunk
2004-07-12 15:56 ` Paolo Ciarrocchi
2004-07-12 16:34 ` Adrian Bunk
2004-07-12 16:43 ` Linus Torvalds
2004-07-12 20:28 ` Paolo Ciarrocchi
2004-07-12 20:22 ` Paolo Ciarrocchi
2004-07-13 20:54 ` cliff white
2004-07-12 21:08 ` Horst von Brand
2004-07-12 11:30 ` is_highmem() and WANT_PAGE_VIRTUAL (was: Re: Linux 2.6.8-rc1) Geert Uytterhoeven
2004-07-12 13:51 ` Andy Whitcroft
2004-07-12 14:23 ` Geert Uytterhoeven
2004-07-12 12:01 ` Linux 2.6.8-rc1 Geert Uytterhoeven
2004-07-12 13:18 ` OGAWA Hirofumi
2004-07-12 13:25 ` Geert Uytterhoeven
2004-07-12 14:02 ` OGAWA Hirofumi
2004-07-12 13:23 ` struct_cpy() and kAFS (was: Re: Linux 2.6.8-rc1) Geert Uytterhoeven
2004-07-12 18:11 ` Andrew Morton
2004-07-12 18:23 ` Christoph Hellwig
2004-07-12 18:40 ` Andrew Morton
2004-07-13 10:14 ` David Howells
2004-07-12 23:49 ` Linux 2.6.8-rc1 (compile stats) John Cherry
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=20040711160019.00c2d658.rddunlap@osdl.org \
--to=rddunlap@osdl.org \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt_domsch@dell.com \
--cc=torvalds@osdl.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
all inboxes | Powered by JetHome®