From: Greg Kroah-Hartman <gregkh@suse.de>
Date: Thu, 3 Mar 2011 01:33:26 +0000 (-0800)
Subject: Staging: hv: mouse_vsc: fix comment coding style
X-Git-Tag: MMI-PSA29.97-13-9~20521^2~312
X-Git-Url: https://git.stricted.de/?a=commitdiff_plain;h=e1f1a0e682bf739f7d2189495265fb3b01f8e85a;p=GitHub%2FMotorolaMobilityLLC%2Fkernel-slsi.git

Staging: hv: mouse_vsc: fix comment coding style

Also mark this as a nice FIXME as we shouldn't ever
care about the value of an atomic variable, which makes me seriously
doubt the validity of this reference counting code.  Odds are it can be
ripped out completly, or at the very least, converted to using a kref.

Cc: Hank Janssen <hjanssen@microsoft.com>
Cc: K. Y. Srinivasan <kys@microsoft.com>
Cc: Haiyang Zhang <haiyangz@microsoft.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
---

diff --git a/drivers/staging/hv/mouse_vsc.c b/drivers/staging/hv/mouse_vsc.c
index 659f118e4f3c..b75066d15ebb 100644
--- a/drivers/staging/hv/mouse_vsc.c
+++ b/drivers/staging/hv/mouse_vsc.c
@@ -157,8 +157,14 @@ static inline struct mousevsc_dev *GetInputDevice(struct hv_device *Device)
 
 	inputDevice = (struct mousevsc_dev *)Device->ext;
 
-//	printk(KERN_ERR "-------------------------> REFCOUNT = %d",
-//	       inputDevice->RefCount);
+/*
+ *	FIXME
+ *	This sure isn't a valid thing to print for debugging, no matter
+ *	what the intention is...
+ *
+ *	printk(KERN_ERR "-------------------------> REFCOUNT = %d",
+ *	       inputDevice->RefCount);
+ */
 
 	if (inputDevice && atomic_read(&inputDevice->RefCount) > 1)
 		atomic_inc(&inputDevice->RefCount);