1. 12 4月, 2011 5 次提交
  2. 11 4月, 2011 1 次提交
  3. 09 4月, 2011 2 次提交
  4. 08 4月, 2011 7 次提交
  5. 07 4月, 2011 21 次提交
  6. 06 4月, 2011 4 次提交
    • J
      HID: Add support for CH Pro Throttle · da60325d
      Jiri Kosina 提交于
      CH Pro Throttle needs NOGET the same way as other products from
      the same vendor require.
      Reported-by: NUnavowed <unavowed@vexillium.org>
      Signed-off-by: NJiri Kosina <jkosina@suse.cz>
      da60325d
    • C
      HID: hid-magicmouse: Increase evdev buffer size · cc5e0f08
      Chase Douglas 提交于
      The evdev buffer isn't big enough when you get many fingers on the
      device. Bump up the buffer to a reasonable size, matching what other
      multitouch devices use. Without this change, events may be discarded in
      the evdev buffer before they are read.
      Reported-by: NSimon Budig <simon@budig.de>
      Cc: Henrik Rydberg <rydberg@euromail.se>
      Cc: Jiri Kosina <jkosina@suse.cz>
      Cc: stable@kernel.org
      Signed-off-by: NChase Douglas <chase.douglas@canonical.com>
      Acked-by: NHenrik Rydberg <rydberg@euromail.se>
      Signed-off-by: NJiri Kosina <jkosina@suse.cz>
      cc5e0f08
    • J
      ide: always ensure that blk_delay_queue() is called if we have pending IO · 782b86e2
      Jens Axboe 提交于
      Just because we are not requeuing a request does not mean that
      some aren't pending. So always issue a blk_delay_queue() if
      either we are requeueing OR there's pending IO.
      
      This fixes a boot problem for some IDE boxes.
      Signed-off-by: NJens Axboe <jaxboe@fusionio.com>
      782b86e2
    • M
      dm: improve block integrity support · a63a5cf8
      Mike Snitzer 提交于
      The current block integrity (DIF/DIX) support in DM is verifying that
      all devices' integrity profiles match during DM device resume (which
      is past the point of no return).  To some degree that is unavoidable
      (stacked DM devices force this late checking).  But for most DM
      devices (which aren't stacking on other DM devices) the ideal time to
      verify all integrity profiles match is during table load.
      
      Introduce the notion of an "initialized" integrity profile: a profile
      that was blk_integrity_register()'d with a non-NULL 'blk_integrity'
      template.  Add blk_integrity_is_initialized() to allow checking if a
      profile was initialized.
      
      Update DM integrity support to:
      - check all devices with _initialized_ integrity profiles match
        during table load; uninitialized profiles (e.g. for underlying DM
        device(s) of a stacked DM device) are ignored.
      - disallow a table load that would result in an integrity profile that
        conflicts with a DM device's existing (in-use) integrity profile
      - avoid clearing an existing integrity profile
      - validate all integrity profiles match during resume; but if they
        don't all we can do is report the mismatch (during resume we're past
        the point of no return)
      Signed-off-by: NMike Snitzer <snitzer@redhat.com>
      Cc: Martin K. Petersen <martin.petersen@oracle.com>
      Signed-off-by: NJens Axboe <jaxboe@fusionio.com>
      a63a5cf8