public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bongani Hlope <bonganilinux@mweb.co.za>
To: LKM <linux-kernel@vger.kernel.org>
Subject: [Patch] Compilation errors on some usb files
Date: 11 Dec 2001 21:47:40 +0200	[thread overview]
Message-ID: <1008100062.3199.3.camel@localhost.localdomain> (raw)

[-- Attachment #1: Type: text/plain, Size: 212 bytes --]

This is the second of the two patches that fixes compilation
errors on linux/drivers/usb/. Like I said on the previous mail,
sorry if this has been fixed already.

This one fixes compilation error on hiddev.c




[-- Attachment #2: usb_hiddev.diff --]
[-- Type: text/x-diff, Size: 1054 bytes --]

--- linux/drivers/usb/hiddev.c	Tue Nov 13 09:23:58 2001
+++ /home/bongani/dev/c/kernel/hiddev.c	Tue Dec 11 21:33:06 2001
@@ -193,7 +193,6 @@
 	struct hiddev_list *list = file->private_data;
 	struct hiddev_list **listptr;
 
-	lock_kernel();
 	listptr = &list->hiddev->list;
 	hiddev_fasync(-1, file, 0);
 
@@ -209,7 +208,6 @@
 	}
 
 	kfree(list);
-	unlock_kernel();
 
 	return 0;
 }
@@ -567,6 +565,7 @@
 	fasync:		hiddev_fasync,
 };
 
+#ifdef CONFIG_USB_HIDDEV
 /*
  * This is where hid.c calls us to connect a hid device to the hiddev driver
  */
@@ -630,6 +629,7 @@
 		hiddev_cleanup(hiddev);
 	}
 }
+#endif
 
 /* Currently this driver is a USB driver.  It's not a conventional one in
  * the sense that it doesn't probe at the USB level.  Instead it waits to
@@ -662,6 +662,7 @@
 	minor:	HIDDEV_MINOR_BASE
 };
 
+#ifdef CONFIG_USB_HIDDEV
 int __init hiddev_init(void)
 {
 	hiddev_devfs_handle =
@@ -675,3 +676,5 @@
 	devfs_unregister(hiddev_devfs_handle);
 	usb_deregister(&hiddev_driver);
 }
+#endif
+

             reply	other threads:[~2001-12-11 19:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-11 19:47 Bongani Hlope [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-12-11 19:47 [Patch] Compilation errors on some usb files Bongani Hlope

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=1008100062.3199.3.camel@localhost.localdomain \
    --to=bonganilinux@mweb.co.za \
    --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