Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Commits on Nov 23, 2010
  1. Merge branch 'configs-2.6.36' into pf-2.6.36

    Oleksandr Natalenko authored
  2. configs-2.6.36: update config for Dell Inspiron 1525

    Oleksandr Natalenko authored
  3. Merge branch 'version-2.6.36' into pf-2.6.36

    Oleksandr Natalenko authored
  4. version-2.6.36: bump to v2.6.36-pf2

    Oleksandr Natalenko authored
  5. Merge remote branch 'tuxonice-2.6.36/combined' into pf-2.6.36

    Oleksandr Natalenko authored
  6. fix merge conflict

    Oleksandr Natalenko authored
Commits on Nov 22, 2010
  1. @NigelCunningham
  2. @gregkh

    Linux 2.6.36.1

    gregkh authored
  3. @gregkh

    sgi-xp: incoming XPC channel messages can come in after the channel's…

    Robin Holt authored gregkh committed
    … partition structures have been torn down
    
    commit 0935897 upstream.
    
    Under some workloads, some channel messages have been observed being
    delayed on the sending side past the point where the receiving side has
    been able to tear down its partition structures.
    
    This condition is already detected in xpc_handle_activate_IRQ_uv(), but
    that information is not given to xpc_handle_activate_mq_msg_uv().  As a
    result, xpc_handle_activate_mq_msg_uv() assumes the structures still exist
    and references them, causing a NULL-pointer deref.
    
    Signed-off-by: Robin Holt <holt@sgi.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  4. @mkl0301 @gregkh

    ARM: cns3xxx: Fixup the missing second parameter to addruart macro to…

    mkl0301 authored gregkh committed
    … allow them to build.
    
    It can't be merged into Linus' tree because this file has already been
    changed in incompatible ways.
    
    Fixup the missing second parameter to addruart macro to allow them to build,
    according to to commit 0e17226.
    
    Enabling DEBUG in head.S would cause:
    rch/arm/boot/compressed/head.S: Assembler messages:
    arch/arm/boot/compressed/head.S:1037: Error: too many positional arguments
    arch/arm/boot/compressed/head.S:1055: Error: too many positional arguments
    
    Signed-off-by: Mac Lin <mkl0301@gmail.com>
    Acked-by: Russell King <rmk+kernel@arm.linux.org.uk>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  5. @rabinv @gregkh

    kgdb,arm: fix register dump

    rabinv authored gregkh committed
    commit 834b296 upstream.
    
    DBG_MAX_REG_NUM incorrectly had the number of indices in the GDB regs
    array rather than the number of registers, leading to an oops when the
    "rd" command is used in KDB.
    
    Signed-off-by: Rabin Vincent <rabin@rab.in>
    Signed-off-by: Jason Wessel <jason.wessel@windriver.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  6. @eparis @gregkh

    secmark: do not return early if there was no error

    eparis authored gregkh committed
    commit 15714f7 upstream.
    
    Commit 4a5a5c7 attempted to pass decent error messages back to userspace for
    netfilter errors.  In xt_SECMARK.c however the patch screwed up and returned
    on 0 (aka no error) early and didn't finish setting up secmark.  This results
    in a kernel BUG if you use SECMARK.
    
    Signed-off-by: Eric Paris <eparis@redhat.com>
    Acked-by: Paul Moore <paul.moore@hp.com>
    Signed-off-by: James Morris <jmorris@namei.org>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  7. @stevedd @gregkh

    Fixed Regression in NFS Direct I/O path

    stevedd authored gregkh committed
    commit 568a810 upstream.
    
    A typo, introduced by commit f11ac8d, in the nfs_direct_write()
    routine causes writes with O_DIRECT set to fail with a ENOMEM error.
    
    Found-by: Jeff Layton <jlayton@redhat.com>
    Signed-off-by: Steve Dickson <steved@redhat.com>
    Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  8. @mikechristie @gregkh

    Fix regressions in scsi_internal_device_block

    mikechristie authored gregkh committed
    commit 986fe6c upstream.
    
    Deleting a SCSI device on a blocked fc_remote_port (before
    fast_io_fail_tmo fires) results in a hanging thread:
    
      STACK:
      0 schedule+1108 [0x5cac48]
      1 schedule_timeout+528 [0x5cb7fc]
      2 wait_for_common+266 [0x5ca6be]
      3 blk_execute_rq+160 [0x354054]
      4 scsi_execute+324 [0x3b7ef4]
      5 scsi_execute_req+162 [0x3b80ca]
      6 sd_sync_cache+138 [0x3cf662]
      7 sd_shutdown+138 [0x3cf91a]
      8 sd_remove+112 [0x3cfe4c]
      9 __device_release_driver+124 [0x3a08b8]
    10 device_release_driver+60 [0x3a0a5c]
    11 bus_remove_device+266 [0x39fa76]
    12 device_del+340 [0x39d818]
    13 __scsi_remove_device+204 [0x3bcc48]
    14 scsi_remove_device+66 [0x3bcc8e]
    15 sysfs_schedule_callback_work+50 [0x260d66]
    16 worker_thread+622 [0x162326]
    17 kthread+160 [0x1680b0]
    18 kernel_thread_starter+6 [0x10aaea]
    
    During the delete, the SCSI device is in moved to SDEV_CANCEL.  When
    the FC transport class later calls scsi_target_unblock, this has no
    effect, since scsi_internal_device_unblock ignores SCSI devics in this
    state.
    
    It looks like all these are regressions caused by:
    5c10e63
    [SCSI] limit state transitions in scsi_internal_device_unblock
    
    Fix by rejecting offline and cancel in the state transition.
    
    Signed-off-by: Christof Schmitt <christof.schmitt@de.ibm.com>
    [jejb: Original patch by Christof Schmitt, modified by Mike Christie]
    Signed-off-by: James Bottomley <James.Bottomley@suse.de>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  9. @gregkh

    Fix race when removing SCSI devices

    Christof Schmitt authored gregkh committed
    commit 546ae79 upstream.
    
    Removing SCSI devices through
    echo 1 > /sys/bus/scsi/devices/ ... /delete
    
    while the FC transport class removes the SCSI target can lead to an
    oops:
    
    Unable to handle kernel pointer dereference at virtual kernel address 00000000b6815000
    Oops: 0011 [#1] PREEMPT SMP DEBUG_PAGEALLOC
    Modules linked in: sunrpc qeth_l3 binfmt_misc dm_multipath scsi_dh dm_mod ipv6 qeth ccwgroup [last unloaded: scsi_wait_scan]
    CPU: 1 Not tainted 2.6.35.5-45.x.20100924-s390xdefault #1
    Process fc_wq_0 (pid: 861, task: 00000000b7331240, ksp: 00000000b735bac0)
    Krnl PSW : 0704200180000000 00000000003ff6e4 (__scsi_remove_device+0x24/0xd0)
               R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:0 CC:2 PM:0 EA:3
    Krnl GPRS: 0000000000000001 0000000000000000 00000000b6815000 00000000bc24a8c0
               00000000003ff7c8 000000000056dbb8 0000000000000002 0000000000835d80
               ffffffff00000000 0000000000001000 00000000b6815000 00000000bc24a7f0
               00000000b68151a0 00000000b6815000 00000000b735bc20 00000000b735bbf8
    Krnl Code: 00000000003ff6d6: a7840001            brc 8,3ff6d8
               00000000003ff6da: a7fbffd8            aghi %r15,-40
               00000000003ff6de: e3e0f0980024        stg %r14,152(%r15)
              >00000000003ff6e4: e31021200004        lg %r1,288(%r2)
               00000000003ff6ea: a71f0000            cghi    %r1,0
               00000000003ff6ee: a7a40011            brc 10,3ff710
               00000000003ff6f2: a7390003            lghi    %r3,3
               00000000003ff6f6: c0e5ffffc8b1        brasl %r14,3f8858
    Call Trace:
    ([<0000000000001000>] 0x1000)
     [<00000000003ff7d2>] scsi_remove_device+0x42/0x54
     [<00000000003ff8ba>] __scsi_remove_target+0xca/0xfc
     [<00000000003ff99a>] __remove_child+0x3a/0x48
     [<00000000003e3246>] device_for_each_child+0x72/0xbc
     [<00000000003ff93a>] scsi_remove_target+0x4e/0x74
     [<0000000000406586>] fc_rport_final_delete+0xb2/0x23c
     [<000000000015d080>] worker_thread+0x200/0x344
     [<000000000016330c>] kthread+0xa0/0xa8
     [<0000000000106c1a>] kernel_thread_starter+0x6/0xc
     [<0000000000106c14>] kernel_thread_starter+0x0/0xc
    INFO: lockdep is turned off.
    Last Breaking-Event-Address:
     [<00000000003ff7cc>] scsi_remove_device+0x3c/0x54
    
    The function __scsi_remove_target iterates through the SCSI devices on
    the host, but it drops the host_lock before calling
    scsi_remove_device. When the SCSI device is deleted from another
    thread, the pointer to the SCSI device in scsi_remove_device can
    become invalid. Fix this by getting a reference to the SCSI device
    before dropping the host_lock to keep the SCSI device alive for the
    call to scsi_remove_device.
    
    Signed-off-by: Christof Schmitt <christof.schmitt@de.ibm.com>
    Signed-off-by: James Bottomley <James.Bottomley@suse.de>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  10. @error27 @gregkh

    gdth: integer overflow in ioctl

    error27 authored gregkh committed
    commit f63ae56 upstream.
    
    gdth_ioctl_alloc() takes the size variable as an int.
    copy_from_user() takes the size variable as an unsigned long.
    gen.data_len and gen.sense_len are unsigned longs.
    On x86_64 longs are 64 bit and ints are 32 bit.
    
    We could pass in a very large number and the allocation would truncate
    the size to 32 bits and allocate a small buffer.  Then when we do the
    copy_from_user(), it would result in a memory corruption.
    
    Signed-off-by: Dan Carpenter <error27@gmail.com>
    Signed-off-by: James Bottomley <James.Bottomley@suse.de>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  11. @gregkh

    pmcraid: remove duplicate struct member

    Anil Ravindranath authored gregkh committed
    commit df30e50 upstream.
    
    sense_buffer is both a direct member of struct pmcraid_cmd as well as
    an indirect one via an anonymous union and struct.  Fix this clash by
    eliminating the direct member in favour of the anonymous struct/union
    one.  The name duplication apparently isn't noticed by gcc versions
    earlier than 4.4
    
    Reported-by: Andi Kleen <ak@linux.intel.com>
    Signed-off-by: Anil Ravindranath <anil_ravindranath@pmc-sierra.com>
    Signed-off-by: James Bottomley <James.Bottomley@suse.de>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  12. @gregkh

    qla4xxx: fix build on PPC

    Jiri Slaby authored gregkh committed
    commit a6751cc upstream.
    
    We use read/write[bslq] but do not include linux/io.h. This causes
    build failures on PPC. Include that file.
    
    Signed-off-by: Jiri Slaby <jslaby@suse.cz>
    Acked-by: Vikas Chaudhary <vikas.chaudhary@qlogic.com>
    Signed-off-by: James Bottomley <James.Bottomley@suse.de>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  13. @davidmilburn @gregkh

    libsas: fix NCQ mixing with non-NCQ

    davidmilburn authored gregkh committed
    commit f0ad30d upstream.
    
    Some cards (like mvsas) have issue troubles if non-NCQ commands are
    mixed with NCQ ones.  Fix this by using the libata default NCQ check
    routine which waits until all NCQ commands are complete before issuing
    a non-NCQ one.  The impact to cards (like aic94xx) which don't need
    this logic should be minimal
    
    Signed-off-by: James Bottomley <James.Bottomley@suse.de>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  14. @gregkh

    sd name space exhaustion causes system hang

    Michael Reed authored gregkh committed
    commit 1a03ae0 upstream.
    
    Following a site power outage which re-enabled all the ports on my FC
    switches, my system subsequently booted with far too many luns!  I had
    let it run hoping it would make multi-user.  It didn't.  :(  It hung solid
    after exhausting the last sd device, sdzzz, and attempting to create sdaaaa
    and beyond.  I was unable to get a dump.
    
    Discovered using a 2.6.32.13 based system.
    
    correct this by detecting when the last index is utilized and failing
    the sd probe of the device.  Patch applies to scsi-misc-2.6.
    
    Signed-off-by: Michael Reed <mdr@sgi.com>
    Signed-off-by: James Bottomley <James.Bottomley@suse.de>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  15. @iksaif @gregkh

    asus-laptop: fix gps rfkill

    iksaif authored gregkh committed
    commit 23f45c3 upstream.
    
    The GPS rfkill crappy code. The ops_data argument wasn't
    set, and was totally misused. The fix have been tested
    on an Asus R2H.
    
    Signed-off-by: Corentin Chary <corentincj@iksaif.net>
    Signed-off-by: Matthew Garrett <mjg@redhat.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  16. @gregkh

    USB: accept some invalid ep0-maxpacket values

    Alan Stern authored gregkh committed
    commit 56626a7 upstream.
    
    A few devices (such as the RCA VR5220 voice recorder) are so
    non-compliant with the USB spec that they have invalid maxpacket sizes
    for endpoint 0.  Nevertheless, as long as we can safely use them, we
    may as well do so.
    
    This patch (as1432) softens our acceptance criterion by allowing
    high-speed devices to have ep0-maxpacket sizes other than 64.  A
    warning is printed in the system log when this happens, and the
    existing error message is clarified.
    
    Signed-off-by: Alan Stern <stern@rowland.harvard.edu>
    Reported-by: James <bjlockie@lockie.ca>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  17. @niwamatsu @gregkh

    usb: r8a66597-hcd: Change mistake of the outsw function

    niwamatsu authored gregkh committed
    commit ac9dfe9 upstream.
    
    Some functions changed by 1c98347.
    However, There was a change mistake of the function (outsw).
    
    Signed-off-by: Nobuhiro Iwamatsu <nobuhiro.iwamatsu.yj@renesas.com>
    CC: Paul Mundt <lethal@linux-sh.org>
    Acked-by: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  18. @gregkh

    USB: opticon: Fix long-standing bugs in opticon driver

    Alon Ziv authored gregkh committed
    commit 97cd8dc upstream.
    
    The bulk-read callback had two bugs:
    a) The bulk-in packet's leading two zeros were returned (and the two last
       bytes truncated)
    b) The wrong URB was transmitted for the second (and later) read requests,
       causing further reads to return the entire packet (including leading
       zeros)
    
    Signed-off-by: Alon Ziv <alon-git@nolaviz.org>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  19. @jhovold @gregkh

    USB: visor: fix initialisation of UX50/TH55 devices

    jhovold authored gregkh committed
    commit cfb8da8 upstream.
    
    Fix regression introduced by commit
    214916f (USB: visor: reimplement using
    generic framework) which broke initialisation of UX50/TH55 devices that
    used re-mapped bulk-out endpoint addresses.
    
    Reported-by: Robert Gadsdon <rgadsdon@bayarea.net>
    Tested-by: Robert Gadsdon <rgadsdon@bayarea.net>
    Signed-off-by: Johan Hovold <jhovold@gmail.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  20. @gregkh

    USB: disable endpoints after unbinding interfaces, not before

    Alan Stern authored gregkh committed
    commit 80f0cf3 upstream.
    
    This patch (as1430) fixes a bug in usbcore.  When a device
    configuration change occurs or a device is removed, the endpoints for
    the old config should be completely disabled.  However it turns out
    they aren't; this is because usb_unbind_interface() calls
    usb_enable_interface() or usb_set_interface() to put interfaces back
    in altsetting 0, which re-enables the interfaces' endpoints.
    
    As a result, when a device goes through a config change or is
    unconfigured, the ep_in[] and ep_out[] arrays may be left holding old
    pointers to usb_host_endpoint structures.  If the device is
    deauthorized these structures get freed, and the stale pointers cause
    errors when the the device is eventually unplugged.
    
    The solution is to disable the endpoints after unbinding the
    interfaces instead of before.  This isn't as large a change as it
    sounds, since usb_unbind_interface() disables all the interface's
    endpoints anyway before calling the driver's disconnect routine,
    unless the driver claims to support "soft" unbind.
    
    This fixes Bugzilla #19192.  Thanks to "Tom" Lei Ming for diagnosing
    the underlying cause of the problem.
    
    Signed-off-by: Alan Stern <stern@rowland.harvard.edu>
    Tested-by: Carsten Sommer <carsten_sommer@ymail.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  21. @plagnioj @gregkh

    USB: atmel_usba_udc: force vbus_pin at -EINVAL when gpio_request failled

    plagnioj authored gregkh committed
    commit 969afff upstream.
    
    to ensure gpio_is_valid return false
    
    Signed-off-by: Nicolas Ferre <nicolas.ferre@atmel.com>
    Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  22. @alars @gregkh

    USB: cp210x: Add WAGO 750-923 Service Cable device ID

    alars authored gregkh committed
    commit 93ad03d upstream.
    
    The WAGO 750-923 USB Service Cable is used for configuration and firmware
    updates of several industrial automation products from WAGO Kontakttechnik GmbH.
    
    Bus 004 Device 002: ID 1be3:07a6
    Device Descriptor:
      bLength                18
      bDescriptorType         1
      bcdUSB               1.10
      bDeviceClass            0 (Defined at Interface level)
      bDeviceSubClass         0
      bDeviceProtocol         0
      bMaxPacketSize0        64
      idVendor           0x1be3
      idProduct          0x07a6
      bcdDevice            1.00
      iManufacturer           1 Silicon Labs
      iProduct                2 WAGO USB Service Cable
      iSerial                 3 1277796751
      . . .
    
    Signed-off-by: Anders Larsen <al@alarsen.net>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  23. @djdelorie @gregkh

    USB: cp210x: Add Renesas RX-Stick device ID

    djdelorie authored gregkh committed
    commit 2f1136d upstream.
    
    RX610 development board by Renesas
    
    Bus 001 Device 024: ID 045b:0053 Hitachi, Ltd
    Device Descriptor:
      bLength                18
      bDescriptorType         1
      bcdUSB               1.10
      bDeviceClass            0 (Defined at Interface level)
      bDeviceSubClass         0
      bDeviceProtocol         0
      bMaxPacketSize0        64
      idVendor           0x045b Hitachi, Ltd
      idProduct          0x0053
      bcdDevice            1.00
      iManufacturer           1 Silicon Labs
      iProduct                2 RX-Stick
      iSerial                 3 0001
      . . .
    
    http://am.renesas.com/rx610stick
    
    Signed-off-by: DJ Delorie <dj@delorie.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  24. @gregkh

    USB: option: Add more ZTE modem USB id's

    Mauro Carvalho Chehab authored gregkh committed
    commit ecfa153 upstream.
    
    There are lots of ZTE USB id's currently not covered by usb/serial. Adds them,
    to allow those devices to work properly on Linux.
    
    While here, put the USB ID's for 0x2002/0x2003 at the sorted order.
    
    This patch is based on zte.c file found on MF645.
    
    PS.: The ZTE driver is commenting the USB ID for 0x0053. It also adds, commented,
    an USB ID for 0x0026.
    
    Not sure why, but I think that 0053 is used by their devices in storage mode only.
    So, I opted to keep the comment on this patch.
    
    Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  25. @gregkh

    USB: Change acm_iad_descriptor bFunctionProtocol to USB_CDC_ACM_PROTO…

    Praveena Nadahally authored gregkh committed
    …_AT_V25TER
    
    commit 5c8db07 upstream.
    
    The protocol code is set 00 in IAD and it's set to 01 in ACM control
    interface descriptor in f_acm.c file. Due to this, windows is unable to
    install the modem(ACM) driver based on class-subclass-protocol matching.
    
    This patch corrects the protocol code in ACM IAD to the same as in
    acm_control_interface_desc protocol code.
    
    Acked-by: Linus Walleij <linus.walleij@stericsson.com>
    Signed-off-by: Praveena Nadahally <praveen.nadahally@stericsson.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  26. @gregkh

    usb: musb: blackfin: call gpio_free() on error path in musb_platform_…

    Sergei Shtylyov authored gregkh committed
    …init()
    
    commit 00be545 upstream.
    
    Blackfin's musb_platform_init() needs to call gpio_free() for error cleanup iff
    otg_get_transceiver() call returns NULL.
    
    Signed-off-by: Sergei Shtylyov <sshtylyov@ru.mvista.com>
    Acked-by: Mike Frysinger <vapier@gentoo.org>
    Signed-off-by: Felipe Balbi <balbi@ti.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  27. @gregkh

    usb: musb: blackfin: call usb_nop_xceiv_unregister() in musb_platform…

    Sergei Shtylyov authored gregkh committed
    …_exit()
    
    commit 3daad24 upstream.
    
    Blackfin's musb_platform_exit() forgets to call usb_nop_xceiv_unregister().
    While fixing this, also remove the unneeded blank line there.
    
    Signed-off-by: Sergei Shtylyov <sshtylyov@ru.mvista.com>
    Acked-by: Mike Frysinger <vapier@gentoo.org>
    Signed-off-by: Felipe Balbi <balbi@ti.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  28. @gregkh

    USB: MUSB: fix kernel WARNING/oops when unloading module in OTG mode

    Sergei Shtylyov authored gregkh committed
    commit f405387 upstream.
    
    Since commit 461972d (musb_core: don't call
    musb_platform_exit() twice), unloading the driver module results in a WARNING
    "kobject: '(null)' (c73de788): is not initialized, yet kobject_put() is being
    called." (or even kernel oops) on e.g. DaVincis, though only in the OTG mode.
    There exists dubious and unbalanced put_device() call in musb_free() which
    takes place only in the OTG mode.  As this commit caused musb_platform_exit()
    to be called (and so unregister the NOP transceiver) before this put_device()
    call, this function references already freed memory.
    
    On the other hand, all the glue layers miss the otg_put_transceiver() call,
    complementary to the otg_get_transceiver() call that they do.  So, I think
    the solution is to get rid of the strange put_device() call, and instead
    call otg_put_transceiver() in the glue layers...
    
    Signed-off-by: Sergei Shtylyov <sshtylyov@ru.mvista.com>
    Signed-off-by: Felipe Balbi <balbi@ti.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
  29. @gregkh

    USB: ftdi_sio: add device ids for ScienceScope

    gregkh authored
    commit 0f266ab upstream.
    
    This adds the requested device ids to the ftdi_sio driver.
    
    Reported-by: Ewan Bingham <ewan@auc.co.uk>
    Cc: Kuba Ober <kuba@mareimbrium.org>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Something went wrong with that request. Please try again.