public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: linux-usb@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: usbutils 0.91 release
Date: Fri, 22 Oct 2010 16:43:22 -0700	[thread overview]
Message-ID: <20101022234322.GA11147@kroah.com> (raw)

Here's the 0.91 release of usbutils.

Big thing is here is the addition of the usbhid-dump tool from Nikolai
Kondrashov, and a bunch of changes to handle USB 3.0 hubs (hopefully)
properly.  Oh, and the build issues on non-Linux systems should be
resolved now as well.

The package can be downladed from kernel.org:
	http://www.kernel.org/pub/linux/utils/usb/usbutils/

We've switched over to using git for development now, which makes things
much easier than the old cvs tree.  The tree 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

-----------

Greg Kroah-Hartman (3):
      add usbhid-dump to the autogen.sh script
      usb.ids: add new device id for qemu audio device
      Minor fixes

Laurent Pinchart (1):
      usbutils: Fix the UVC bmInterlaceFlags field decoding

Mike Frysinger (2):
      usbutils.pc: use datarootdir
      fix building on non-Linux systems (e.g. BSD)

Nikolai Kondrashov (1):
      Integrate usbhid-dump

Sarah Sharp (5):
      usbutils: Fix Wireless USB descriptor fetching.
      usbutils: Support USB 3.0 hub descriptor output.
      usbutils: Print MaxStreams and Mult for USB 3.0 devices.
      usbutils: Print Binary Object Store descriptor.
      usbutils: Fix bug in link state description printing.



                 reply	other threads:[~2010-10-22 23:42 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=20101022234322.GA11147@kroah.com \
    --to=greg@kroah.com \
    --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