| commit | 27ae4d4328769021b95777e37873074c1da52f91 | |
| author | Daniel Walker <dwalker@mvista.com> | |
| Sat, 22 Dec 2007 04:16:15 +0000 (21 20:16 -0800) | ||
| committer | David S. Miller <davem@davemloft.net> | |
| Mon, 28 Jan 2008 23:09:12 +0000 (28 15:09 -0800) | ||
| tree | 288973678d482a731eee32c15abfee9a3b4562e0 | treesnapshot (tar.gz zip) |
| parent | 772353d84991ecd2eebc2e287c381cb1626f9209 | commitdiff |
prism54: remove questionable down_interruptible usage
Reviewing the semaphore usage I noticed these down_interruptible calls. Most
of these aren't returning anything, so a caller can't tell if the operation
completed or not. prism54_wpa_bss_ie_get() returns zero, but it's treated as
the function failing which doesn't seem correct.
Signed-off-by: Daniel Walker <dwalker@mvista.com>
Cc: Michael Wu <flamingice@sourmilk.net>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
Reviewing the semaphore usage I noticed these down_interruptible calls. Most
of these aren't returning anything, so a caller can't tell if the operation
completed or not. prism54_wpa_bss_ie_get() returns zero, but it's treated as
the function failing which doesn't seem correct.
Signed-off-by: Daniel Walker <dwalker@mvista.com>
Cc: Michael Wu <flamingice@sourmilk.net>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
| drivers/net/wireless/prism54/isl_ioctl.c | diffblobblamehistory |