From: Matt Tolentino <metolent@snoqualmie.dp.intel.com>
To: akpm@osdl.org
Cc: bjorn.helgaas@hp.com, linux-ia64@vger.kernel.org,
linux-kernel@vger.kernel.org, Matt_Domsch@dell.com,
matthew.e.tolentino@intel.com
Subject: [patch 3/3] efivars driver update and move
Date: Thu, 22 Apr 2004 10:36:11 -0700 [thread overview]
Message-ID: <200404221736.i3MHaBeQ023389@snoqualmie.dp.intel.com> (raw)
Third efivars driver update patch that removes x86 references
to the /proc version of the driver...
matt
diff -urN linux-2.6.6-rc2/arch/i386/kernel/efi.c linux-2.6.6-rc2-mod/arch/i386/kernel/efi.c
--- linux-2.6.6-rc2/arch/i386/kernel/efi.c 2004-04-20 14:29:43.000000000 -0700
+++ linux-2.6.6-rc2-mod/arch/i386/kernel/efi.c 2004-04-21 00:39:39.276757760 -0700
@@ -28,7 +28,7 @@
#include <linux/spinlock.h>
#include <linux/bootmem.h>
#include <linux/ioport.h>
-#include <linux/proc_fs.h>
+#include <linux/module.h>
#include <linux/efi.h>
#include <asm/setup.h>
@@ -46,6 +46,7 @@
extern efi_status_t asmlinkage efi_call_phys(void *, ...);
struct efi efi;
+EXPORT_SYMBOL(efi);
struct efi efi_phys __initdata;
struct efi_memory_map memmap __initdata;
@@ -55,18 +56,6 @@
extern void * boot_ioremap(unsigned long, unsigned long);
/*
- * efi_dir is allocated here, but the directory isn't created
- * here, as proc_mkdir() doesn't work this early in the bootup
- * process. Therefore, each module, like efivars, must test for
- * if (!efi_dir) efi_dir = proc_mkdir("efi", NULL);
- * prior to creating their own entries under /proc/efi.
- */
-#ifdef CONFIG_PROC_FS
-struct proc_dir_entry *efi_dir;
-#endif
-
-
-/*
* To make EFI call EFI runtime service in physical addressing mode we need
* prelog/epilog before/after the invocation to disable interrupt, to
* claim EFI runtime service handler exclusively and to duplicate a memory in
reply other threads:[~2004-04-22 15:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200404221736.i3MHaBeQ023389@snoqualmie.dp.intel.com \
--to=metolent@snoqualmie.dp.intel.com \
--cc=Matt_Domsch@dell.com \
--cc=akpm@osdl.org \
--cc=bjorn.helgaas@hp.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew.e.tolentino@intel.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
all inboxes | Powered by JetHome®