From: Brian Maly <bmaly@redhat.com>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org, ying.huang@intel.com
Subject: Re: [PATCH] fix DMI for EFI
Date: Tue, 03 Mar 2009 21:55:31 -0500 [thread overview]
Message-ID: <49ADEDA3.1030406@redhat.com> (raw)
In-Reply-To: <86802c440902281856h1dc950e7me8568cd5dca59da9@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 218 bytes --]
New patch. Its easier I think to just move efi_init() earlier. Seems
less risky and less drawbacks.
Signed-off-by: Brian Maly <bmaly@redhat>
setup.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
[-- Attachment #2: fix-DMI-for-EFI-2.6.29.patch --]
[-- Type: text/x-patch, Size: 575 bytes --]
--- a/arch/x86/kernel/setup.c 2009-03-03 21:24:53.000000000 -0500
+++ b/arch/x86/kernel/setup.c 2009-03-03 21:26:00.000000000 -0500
@@ -770,6 +770,9 @@ void __init setup_arch(char **cmdline_p)
finish_e820_parsing();
+ if (efi_enabled)
+ efi_init();
+
dmi_scan_machine();
dmi_check_system(bad_bios_dmi_table);
@@ -789,8 +792,6 @@ void __init setup_arch(char **cmdline_p)
insert_resource(&iomem_resource, &data_resource);
insert_resource(&iomem_resource, &bss_resource);
- if (efi_enabled)
- efi_init();
#ifdef CONFIG_X86_32
if (ppro_with_ram_bug()) {
next prev parent reply other threads:[~2009-03-04 2:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-01 2:40 [PATCH] fix DMI for EFI Brian Maly
2009-03-01 2:56 ` Yinghai Lu
2009-03-01 3:11 ` Brian Maly
2009-03-01 3:25 ` Yinghai Lu
2009-03-01 3:58 ` Brian Maly
2009-03-04 2:55 ` Brian Maly [this message]
2009-03-04 11:00 ` Ingo Molnar
2009-03-04 15:03 ` Brian Maly
2009-03-04 17:54 ` Ingo Molnar
2009-03-04 18:00 ` Brian Maly
2009-03-04 18:02 ` Ingo Molnar
2009-03-05 1:33 ` Huang Ying
2009-03-05 10:05 ` Ingo Molnar
2009-03-04 17:57 ` [tip:x86/urgent] x86: fix DMI on EFI Brian Maly
-- strict thread matches above, loose matches on Subject: below --
2009-03-01 1:33 [PATCH] fix DMI for EFI Brian Maly
2009-03-01 2:01 ` Kyle McMartin
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=49ADEDA3.1030406@redhat.com \
--to=bmaly@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=ying.huang@intel.com \
--cc=yinghai@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 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.