From: Greg KH <gregkh@linuxfoundation.org>
To: linux-usb@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: usbutils 007 release
Date: Thu, 6 Jun 2013 16:40:57 -0700 [thread overview]
Message-ID: <20130606234057.GA14840@kroah.com> (raw)
Here's the 007 release of usbutils.
Nothing major over the 006 release, just a bunch of tiny bug fixes that
have trickled in over the past year. The short changelog can be found
below.
The package can be downladed from kernel.org:
http://www.kernel.org/pub/linux/utils/usb/usbutils/
The source tree for usbutils can be found on both kernel.org and
github.com if you want to fork it and send us changes easier:
http://git.kernel.org/?p=linux/kernel/git/gregkh/usbutils.git
http://github.com/gregkh/usbutils/tree/master
thanks,
greg k-h
-----------
Aurelien Jarno (1):
usb-devices: correctly quote driver path
Bjørn Mork (4):
lsusb: decode CDC MBIM descriptor
lsusb: decode CDC NCM functional descriptor
lsusb: decode CDC Command Set descriptor
usb-devices: avoid numbers being seen as octal by printf
Daniel Mack (1):
lsusb: parse bmFormats inside UAC2 interface headers as hex
Greg Kroah-Hartman (12):
do_release notes
Merge pull request #11 from bmork/mbim
update of usb.ids file from upstream
Merge pull request #13 from bmork/for-greg
remove devtree logic
Merge pull request #14 from SpecLad/master
Merge pull request #16 from zonque/uac2
Merge pull request #15 from lnykryn/master
Merge pull request #17 from hegge/uac1-misplaced-endpoint
Merge pull request #18 from jethrogb/master
usb.ids update
usb.ids add BlueZ Host stack device id.
Jethro Beekman (1):
Fix lsusb -t potentially not listing all devices
Lukas Nykryn (1):
lsusb-t: make sure that interfaces are added to lists only once
Sarah Sharp (2):
lsusb: Fix USB 3.0 link state reporting.
lsusb: Fix bug in USB 2.0 extended caps descriptor.
Torstein Hegge (1):
lsusb: Parse misplaced UAC1 AudioControl Endpoint Descriptor
Роман Донченко (1):
lsusb: Support non-ASCII string descriptors.
reply other threads:[~2013-06-06 23:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130606234057.GA14840@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox