1. 15 10月, 2008 14 次提交
  2. 23 7月, 2008 2 次提交
  3. 22 4月, 2008 2 次提交
    • J
      HID: fix sparse warnings · 282bfd4c
      Jiri Slaby 提交于
      Fix these sparse warnings:
      .../hid/hid-core.c:100:15: warning: incorrect type in assignment (different signedness)
      .../hid/hid-core.c:100:15:    expected signed int [usertype] *value
      .../hid/hid-core.c:100:15:    got unsigned int *<noident>
              by unsigned -> s32
      
      .../hid/hid-input-quirks.c:336:10: warning: Using plain integer as NULL pointer
              by 0 -> NULL
      
      .../hid/usbhid/hid-core.c:786:46: warning: incorrect type in argument 3 (different signedness)
      .../hid/usbhid/hid-core.c:786:46:    expected int *max
      .../hid/usbhid/hid-core.c:786:46:    got unsigned int *<noident>
      .../hid/usbhid/hid-core.c:787:47: warning: incorrect type in argument 3 (different signedness)
      .../hid/usbhid/hid-core.c:787:47:    expected int *max
      .../hid/usbhid/hid-core.c:787:47:    got unsigned int *<noident>
      .../hid/usbhid/hid-core.c:788:48: warning: incorrect type in argument 3 (different signedness)
      .../hid/usbhid/hid-core.c:788:48:    expected int *max
      .../hid/usbhid/hid-core.c:788:48:    got unsigned int *<noident>
              by int -> unsigned int
      Signed-off-by: NJiri Slaby <jirislaby@gmail.com>
      Signed-off-by: NJiri Kosina <jkosina@suse.cz>
      282bfd4c
    • J
      HID: Sunplus Wireless Desktop needs report descriptor fixup · 5f1ab74f
      Jiri Kosina 提交于
      This device has reports lower logical maximum compared to the real
      usages for Zoom+ and Zoom- it emits.
      
      This patch bumps the values in the report descriptor up, and also
      adjusts HID_MAX_USAGE accordingly.
      Reported-by: NKhelben Blackstaff <eye.of.the.8eholder@gmail.com>
      Signed-off-by: NJiri Kosina <jkosina@suse.cz>
      5f1ab74f
  4. 11 2月, 2008 1 次提交
    • J
      HID: fix processing of event quirks · 68a1f2cc
      Jiri Kosina 提交于
      The old code (before move) stopped further processing of the
      event after it has been already processed by the quirk handler.
      
      The new code didn't propagate the return value properly, and
      therefore the processing always proceeded, which was wrong.
      
      This patch fixes it. Pointed out in kernel.org bugzilla #9842
      Signed-off-by: NJiri Kosina <jkosina@suse.cz>
      68a1f2cc
  5. 28 1月, 2008 8 次提交