linux-kernel - [GIT PATCH] USB fixes for 2.6.18-rc6

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <20060907222706.GA8886@kroah.com>
Date:	Thu, 7 Sep 2006 15:27:06 -0700
From:	Greg KH <gregkh@...e.de>
To:	Linus Torvalds <torvalds@...l.org>, Andrew Morton <akpm@...l.org>
Cc:	linux-kernel@...r.kernel.org, linux-usb-devel@...ts.sourceforge.net
Subject: [GIT PATCH] USB fixes for 2.6.18-rc6

Here are a some fixes for USB against 2.6.18-rc6.  They do the
following:
	- build warning fix in the usbhid driver
	- usb touchscreen bugfix
	- new device id added to the ftdi_sio driver
	- new device id added to the sisusbvga driver

Please pull from:
	master.kernel.org:/pub/scm/linux/kernel/git/gregkh/usb-2.6.git/

The full patches will be sent to the linux-usb-devel mailing list, if
anyone wants to see them.

thanks,

greg k-h


 drivers/usb/input/hid-core.c        |    4 ++--
 drivers/usb/input/usbtouchscreen.c  |    2 +-
 drivers/usb/misc/sisusbvga/sisusb.c |    2 ++
 drivers/usb/serial/ftdi_sio.c       |    1 +
 drivers/usb/serial/ftdi_sio.h       |    5 +++++
 5 files changed, 11 insertions(+), 3 deletions(-)

---------------

Adrian Bunk:
      USB: hid-core.c: fix duplicate USB_DEVICE_ID_GTCO_404

Kai Lindhom:
      usbtouchscreen: fix ITM data reading

Nobuhiro Iwamatsu:
      USB: Support for USB20SVGA-WH & USB20SVGA-DG

Ralf Schlatterbeck:
      USB: New device ID for ftdi_sio usb serial driver

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/