1. 28 Aug, 2013 19 commits
  2. 27 Aug, 2013 14 commits
  3. 26 Aug, 2013 7 commits
    • Lidza Louina's avatar
      staging: dgnc: tty.c: edits var in init func for sparse · e7f1c932
      Lidza Louina authored
      This patch edits the vaddr variable in dgnc_tty_init.
      The variable gets set to board_t->re_map_membase. A
      previous patch changed the re_map_membase variable's
      marker and type. This patch makes sure that the
      changes are consistent and that it doesn't cause
      sparse warnings.
      Signed-off-by: default avatarLidza Louina <lidza.louina@gmail.com>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      e7f1c932
    • Lidza Louina's avatar
      staging: dgnc: neo.c: changes param in neo_read_eeprom function for sparse · c2ac546e
      Lidza Louina authored
      This patch adds a marker to neo_read_eeprom function's
      base parameter.
      
      It removes these warnings found in neo.c:
      
      warning: incorrect type in argument 1 (different address spaces)
        expected unsigned char *base
        got unsigned char [noderef] [usertype] <asn:2>*re_map_membase
      warning: incorrect type in argument 2 (different address spaces)
        expected void volatile [noderef] <asn:2>*addr
        got unsigned char *
      
      These warnings happen because this function gets
      called with a board_t->re_map_base variable. A previous
      patch added the __iomem marker to this variable. This
      patch ensures that the changes are consistent.
      Signed-off-by: default avatarLidza Louina <lidza.louina@gmail.com>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      c2ac546e
    • Lidza Louina's avatar
      staging: dgnc: cls.c: changes var in cls_vpd function for sparse · 68b146e8
      Lidza Louina authored
      This patch changes cls_vpd function's re_map_vpdbase variable
      type and marker.
      
      It removes these warnings found in cls.c:
      
      warning: incorrect type in assignment (different address spaces)
        expected unsigned char [usertype] *re_map_vpdbase
        got void [noderef] <asn:2>*
      warning: incorrect type in argument 1 (different address spaces)
        expected void const volatile [noderef] <asn:2>*addr
        got unsigned char [usertype] *
      warning: incorrect type in argument 1 (different address spaces)
        expected void volatile [noderef] <asn:2>*addr
        got unsigned char [usertype] *re_map_vpdbase
      
      The variables passed to readb needs to be of type u8
      with a __iomem marker. re_map_vpdbase is passed into
      readb in the code.
      Signed-off-by: default avatarLidza Louina <lidza.louina@gmail.com>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      68b146e8
    • Lidza Louina's avatar
      staging: dgnc: driver.h: changes a struct board_t var's type and marker for sparse · 7915dea7
      Lidza Louina authored
      This patch changes the board_t->re_map_membase variable
      type and marker.
      
      It removes these warnings found in the neo.c,
      driver.c and cls.c files:
      
      warning: incorrect type in argument 1 (different address spaces)
        expected void const volatile [noderef] <asn:2>*addr
        got unsigned char volatile *<noident>
      warning: incorrect type in argument 2 (different address spaces)
        expected void volatile [noderef] <asn:2>*addr
        got unsigned char volatile *<noident>
      
      The variables passed to readb and writeb need to
      be of type u8 with a __iomem marker. These warnings
      were popping up everytime the readb and writeb
      functions were called with a
      board_t->re_map_membase variable.
      
      The change made to the driver.h file adds the marker
      and changes the variable type.
      Signed-off-by: default avatarLidza Louina <lidza.louina@gmail.com>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      7915dea7
    • Lidza Louina's avatar
      staging: dgnc: neo_uart_struct: adds marker and changes vars' types for sparse · 2587771a
      Lidza Louina authored
      This patch fixes these warnings found in the neo.c file:
      
      warning: incorrect type in argument 1 (different address spaces)
        expected void const volatile [noderef] <asn:2>*addr
        got unsigned char volatile *<noident>
      warning: incorrect type in argument 2 (different address spaces)
        expected void volatile [noderef] <asn:2>*addr
        got unsigned char volatile *<noident>
      
      The variables passed to readb and writeb need to
      be of type u8 with a __iomem marker. These warnings
      were popping up everytime the readb and writeb
      functions were called with a neo_uart_struct variable.
      
      The change made to the driver.h file adds the marker
      to the neo_uart_struct and the changes in neo.h
      changes the variables' types.
      Signed-off-by: default avatarLidza Louina <lidza.louina@gmail.com>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      2587771a
    • Lidza Louina's avatar
      staging: dgnc: cls_uart_struct: adds marker and changes vars' types for sparse · 2ea550bd
      Lidza Louina authored
      This patch removes these sparse warnings found in the cls.c file:
      
      warning: incorrect type in argument 1 (different address spaces)
        expected void const volatile [noderef] <asn:2>*addr
        got unsigned char volatile *<noident>
      warning: incorrect type in argument 2 (different address spaces)
        expected void volatile [noderef] <asn:2>*addr
        got unsigned char volatile *<noident>
      
      The variables passed to readb and writeb need to
      be of type u8 with a __iomem marker. These warnings
      were popping up everytime the readb and writeb
      functions were called with a cls_uart_struct variable.
      
      The change made to the driver.h file adds the marker
      to the cls_uart_struct and the changes in cls.h
      changes its variables' types.
      Signed-off-by: default avatarLidza Louina <lidza.louina@gmail.com>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      2ea550bd
    • Greg Kroah-Hartman's avatar
      staging: usbip: use DEVICE_ATTR_RO/RW for sysfs attributes · b1f56aca
      Greg Kroah-Hartman authored
      It's easier to audit the sysfs files if they use the RO/RW macros, so
      convert the usbip code to them.
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      b1f56aca