From: Matt Domsch <Matt_Domsch@dell.com>
To: akpm@osdl.org
Cc: linux-kernel@vger.kernel.org
Subject: efivars: add MODULE_VERSION, remove unnecessary check in exit
Date: Mon, 17 May 2004 15:24:11 -0500 [thread overview]
Message-ID: <20040517202411.GB19268@lists.us.dell.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1651 bytes --]
* Adds MODULE_VERSION
* Remove check for efi_enabled in efivars_exit() - we aborted module
load at init based on this already.
--
Matt Domsch
Sr. Software Engineer, Lead Engineer
Dell Linux Solutions linux.dell.com & www.dell.com/linux
Linux on Dell mailing lists @ http://lists.us.dell.com
===== drivers/firmware/efivars.c 1.4 vs edited =====
--- 1.4/drivers/firmware/efivars.c Sat May 15 01:11:54 2004
+++ edited/drivers/firmware/efivars.c Mon May 17 14:38:25 2004
@@ -23,6 +23,10 @@
*
* Changelog:
*
+ * 17 May 2004 - Matt Domsch <Matt_Domsch@dell.com>
+ * remove check for efi_enabled in exit
+ * add MODULE_VERSION
+ *
* 26 Apr 2004 - Matt Domsch <Matt_Domsch@dell.com>
* minor bug fixes
*
@@ -77,11 +81,13 @@
#include <asm/uaccess.h>
+#define EFIVARS_VERSION "0.08"
+#define EFIVARS_DATE "2004-May-17"
+
MODULE_AUTHOR("Matt Domsch <Matt_Domsch@Dell.com>");
MODULE_DESCRIPTION("sysfs interface to EFI Variables");
MODULE_LICENSE("GPL");
-
-#define EFIVARS_VERSION "0.07 2004-Apr-26"
+MODULE_VERSION(EFIVARS_VERSION);
/*
* efivars_lock protects two things:
@@ -667,7 +673,8 @@
if (!efi_enabled)
return -ENODEV;
- printk(KERN_INFO "EFI Variables Facility v%s\n", EFIVARS_VERSION);
+ printk(KERN_INFO "EFI Variables Facility v%s %s\n", EFIVARS_VERSION,
+ EFIVARS_DATE);
/*
* For now we'll register the efi subsys within this driver
@@ -735,9 +742,6 @@
efivars_exit(void)
{
struct list_head *pos, *n;
-
- if (!efi_enabled)
- return;
list_for_each_safe(pos, n, &efivar_list)
efivar_unregister(get_efivar_entry(pos));
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
reply other threads:[~2004-05-17 20:24 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=20040517202411.GB19268@lists.us.dell.com \
--to=matt_domsch@dell.com \
--cc=akpm@osdl.org \
--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
all inboxes | Powered by JetHome®