1. 25 Jan, 2013 31 commits
  2. 24 Jan, 2013 5 commits
  3. 22 Jan, 2013 4 commits
    • Mark Einon's avatar
      staging: et131x: Fix all sparse warnings · c0594ee9
      Mark Einon authored
      Dan Carpenter has pointed out that there are several sparse warnings
      from et131x.c, listed below. This patch fixes all these errors.
      
      drivers/staging/et131x/et131x.c:1870:33: warning: incorrect type in assignment (different address spaces)
      drivers/staging/et131x/et131x.c:1870:33:    expected unsigned int [usertype] *num_des
      drivers/staging/et131x/et131x.c:1870:33:    got unsigned int [noderef] <asn:2>*<noident>
      drivers/staging/et131x/et131x.c:1871:37: warning: incorrect type in assignment (different address spaces)
      drivers/staging/et131x/et131x.c:1871:37:    expected unsigned int [usertype] *full_offset
      drivers/staging/et131x/et131x.c:1871:37:    got unsigned int [noderef] <asn:2>*<noident>
      drivers/staging/et131x/et131x.c:1872:33: warning: incorrect type in assignment (different address spaces)
      drivers/staging/et131x/et131x.c:1872:33:    expected unsigned int [usertype] *min_des
      drivers/staging/et131x/et131x.c:1872:33:    got unsigned int [noderef] <asn:2>*<noident>
      drivers/staging/et131x/et131x.c:1873:33: warning: incorrect type in assignment (different address spaces)
      drivers/staging/et131x/et131x.c:1873:33:    expected unsigned int [usertype] *base_hi
      drivers/staging/et131x/et131x.c:1873:33:    got unsigned int [noderef] <asn:2>*<noident>
      drivers/staging/et131x/et131x.c:1874:33: warning: incorrect type in assignment (different address spaces)
      drivers/staging/et131x/et131x.c:1874:33:    expected unsigned int [usertype] *base_lo
      drivers/staging/et131x/et131x.c:1874:33:    got unsigned int [noderef] <asn:2>*<noident>
      drivers/staging/et131x/et131x.c:1876:33: warning: incorrect type in assignment (different address spaces)
      drivers/staging/et131x/et131x.c:1876:33:    expected unsigned int [usertype] *num_des
      drivers/staging/et131x/et131x.c:1876:33:    got unsigned int [noderef] <asn:2>*<noident>
      drivers/staging/et131x/et131x.c:1877:37: warning: incorrect type in assignment (different address spaces)
      drivers/staging/et131x/et131x.c:1877:37:    expected unsigned int [usertype] *full_offset
      drivers/staging/et131x/et131x.c:1877:37:    got unsigned int [noderef] <asn:2>*<noident>
      drivers/staging/et131x/et131x.c:1878:33: warning: incorrect type in assignment (different address spaces)
      drivers/staging/et131x/et131x.c:1878:33:    expected unsigned int [usertype] *min_des
      drivers/staging/et131x/et131x.c:1878:33:    got unsigned int [noderef] <asn:2>*<noident>
      drivers/staging/et131x/et131x.c:1879:33: warning: incorrect type in assignment (different address spaces)
      drivers/staging/et131x/et131x.c:1879:33:    expected unsigned int [usertype] *base_hi
      drivers/staging/et131x/et131x.c:1879:33:    got unsigned int [noderef] <asn:2>*<noident>
      drivers/staging/et131x/et131x.c:1880:33: warning: incorrect type in assignment (different address spaces)
      drivers/staging/et131x/et131x.c:1880:33:    expected unsigned int [usertype] *base_lo
      drivers/staging/et131x/et131x.c:1880:33:    got unsigned int [noderef] <asn:2>*<noident>
      drivers/staging/et131x/et131x.c:1898:24: warning: incorrect type in argument 2 (different address spaces)
      drivers/staging/et131x/et131x.c:1898:24:    expected void volatile [noderef] <asn:2>*addr
      drivers/staging/et131x/et131x.c:1898:24:    got unsigned int [usertype] *base_hi
      drivers/staging/et131x/et131x.c:1900:24: warning: incorrect type in argument 2 (different address spaces)
      drivers/staging/et131x/et131x.c:1900:24:    expected void volatile [noderef] <asn:2>*addr
      drivers/staging/et131x/et131x.c:1900:24:    got unsigned int [usertype] *base_lo
      drivers/staging/et131x/et131x.c:1901:60: warning: incorrect type in argument 2 (different address spaces)
      drivers/staging/et131x/et131x.c:1901:60:    expected void volatile [noderef] <asn:2>*addr
      drivers/staging/et131x/et131x.c:1901:60:    got unsigned int [usertype] *num_des
      drivers/staging/et131x/et131x.c:1902:39: warning: incorrect type in argument 2 (different address spaces)
      drivers/staging/et131x/et131x.c:1902:39:    expected void volatile [noderef] <asn:2>*addr
      drivers/staging/et131x/et131x.c:1902:39:    got unsigned int [usertype] *full_offset
      drivers/staging/et131x/et131x.c:1910:24: warning: incorrect type in argument 2 (different address spaces)
      drivers/staging/et131x/et131x.c:1910:24:    expected void volatile [noderef] <asn:2>*addr
      drivers/staging/et131x/et131x.c:1910:24:    got unsigned int [usertype] *min_des
      drivers/staging/et131x/et131x.c:2583:32: warning: incorrect type in assignment (different address spaces)
      drivers/staging/et131x/et131x.c:2583:32:    expected unsigned int [usertype] *offset
      drivers/staging/et131x/et131x.c:2583:32:    got unsigned int [noderef] <asn:2>*<noident>
      drivers/staging/et131x/et131x.c:2585:32: warning: incorrect type in assignment (different address spaces)
      drivers/staging/et131x/et131x.c:2585:32:    expected unsigned int [usertype] *offset
      drivers/staging/et131x/et131x.c:2585:32:    got unsigned int [noderef] <asn:2>*<noident>
      drivers/staging/et131x/et131x.c:2602:24: warning: incorrect type in argument 2 (different address spaces)
      drivers/staging/et131x/et131x.c:2602:24:    expected void volatile [noderef] <asn:2>*addr
      drivers/staging/et131x/et131x.c:2602:24:    got unsigned int [usertype] *offset
      drivers/staging/et131x/et131x.c:4093:13: warning: symbol 'et131x_isr' was not declared. Should it be static?
      Reported-by: default avatarDan Carpenter <dan.carpenter@oracle.com>
      Signed-off-by: default avatarMark Einon <mark.einon@gmail.com>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      c0594ee9
    • Harvey Yang's avatar
      staging: usbip: replace the interrupt safe spinlocks with common ones. · 50b66b5c
      Harvey Yang authored
      On the client side, we have a virtual hcd driver, there actually no
      hardware interrupts, so we do not need worry about race conditions
      caused by irq with spinlock held. Turning off irq is not good for system
      performance after all. Just replace them with a non interrupt safe
      version.
      Signed-off-by: default avatarHarvey Yang <harvey.huawei.yang@gmail.com>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      50b66b5c
    • Harvey Yang's avatar
      staging: usbip: use interrupt safe spinlock to avoid potential deadlock. · dcf14779
      Harvey Yang authored
      The function 'usbip_event_add()' may be called in interrupt context on
      the stub side:
      'stub_complete'->'stub_enqueue_ret_unlink'->'usbip_event_add'.
      In this function it tries to get the lock 'ud->lock', so we should
      disable irq when we get this lock in process context.
      Signed-off-by: default avatarHarvey Yang <harvey.huawei.yang@gmail.com>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      dcf14779
    • Mark Einon's avatar
      staging: et131x: Modify block comments to fit with networking style · 26ef1021
      Mark Einon authored
      In preparation for moving et131x to drivers/net, fixup the block
      comments to match the preferred networking style - no /* on separate
      line, but */ are on a seperate line.
      Signed-off-by: default avatarMark Einon <mark.einon@gmail.com>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      26ef1021