All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: linux-ia64@vger.kernel.org
Subject: [PATCH] Trivial 2.5 efivars.c whitespace cleanup
Date: Wed, 13 Aug 2003 22:11:44 +0000	[thread overview]
Message-ID: <marc-linux-ia64-106081285931321@msgid-missing> (raw)

Against linux-2.5.  Convert leading spaces to tabs.

=== arch/ia64/kernel/efivars.c 1.12 vs edited ==--- 1.12/arch/ia64/kernel/efivars.c	Mon Jun 23 01:09:40 2003
+++ edited/arch/ia64/kernel/efivars.c	Wed Aug 13 17:12:55 2003
@@ -168,13 +168,12 @@
 			 efi_char16_t *variable_name,
 			 efi_guid_t *vendor_guid)
 {
-
 	int i, short_name_size = variable_name_size / sizeof(efi_char16_t) + 38;
 	char *short_name;
 	efivar_entry_t *new_efivar;
 
-        short_name = kmalloc(short_name_size+1, GFP_KERNEL);
-        new_efivar = kmalloc(sizeof(efivar_entry_t), GFP_KERNEL);
+	short_name = kmalloc(short_name_size+1, GFP_KERNEL);
+	new_efivar = kmalloc(sizeof(efivar_entry_t), GFP_KERNEL);
 
 	if (!short_name || !new_efivar)  {
 		if (short_name)        kfree(short_name);
@@ -210,9 +209,9 @@
 	new_efivar->entry->read_proc = efivar_read;
 	new_efivar->entry->write_proc = efivar_write;
 
-        spin_lock(&efivars_lock);
-        list_add(&new_efivar->list, &efivar_list);
-        spin_unlock(&efivars_lock);
+	spin_lock(&efivars_lock);
+	list_add(&new_efivar->list, &efivar_list);
+	spin_unlock(&efivars_lock);
 
 	return 0;
 }
@@ -283,7 +282,7 @@
 	if (!var_data)
 		return -ENOMEM;
 	if (copy_from_user(var_data, buffer, size)) {
-                kfree(var_data);
+		kfree(var_data);
 		return -EFAULT;
 	}
 
@@ -349,7 +348,6 @@
 static int __init
 efivars_init(void)
 {
-
 	efi_status_t status;
 	efi_guid_t vendor_guid;
 	efi_char16_t *variable_name = kmalloc(1024, GFP_KERNEL);
@@ -357,13 +355,13 @@
 
 	printk(KERN_INFO "EFI Variables Facility v%s\n", EFIVARS_VERSION);
 
-        /* Since efi.c happens before procfs is available,
-           we create the directory here if it doesn't
-           already exist.  There's probably a better way
-           to do this.
-        */
-        if (!efi_dir)
-                efi_dir = proc_mkdir("efi", NULL);
+	/* Since efi.c happens before procfs is available,
+	   we create the directory here if it doesn't
+	   already exist.  There's probably a better way
+	   to do this.
+	*/
+	if (!efi_dir)
+		efi_dir = proc_mkdir("efi", NULL);
 
 	efi_vars_dir = proc_mkdir("vars", efi_dir);
 
@@ -407,7 +405,7 @@
 	struct list_head *pos, *n;
 	efivar_entry_t *efivar;
 
-        spin_lock(&efivars_lock);
+	spin_lock(&efivars_lock);
 	list_for_each_safe(pos, n, &efivar_list) {
 		efivar = efivar_entry(pos);
 		remove_proc_entry(efivar->entry->name, efi_vars_dir);


                 reply	other threads:[~2003-08-13 22:11 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=marc-linux-ia64-106081285931321@msgid-missing \
    --to=bjorn.helgaas@hp.com \
    --cc=linux-ia64@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 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.