mirror of https://lore.kernel.org/lkml/
 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.87 release
Date: Wed, 17 Mar 2010 18:51:09 -0700	[thread overview]
Message-ID: <20100318015109.GB28263@kroah.com> (raw)

Here's the 0.87 release of usbutils.

There are some fixes for people having problems with the latest libusb
version, minor code edits, and some new USB class logic.  The whole
changelog is below.

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

-----------

Shortlog of changes since last release (0.86):

Aurelien Jarno (1):
      lsusb.c: correctly dump ccid devices

Greg Kroah-Hartman (11):
      lots of trailing whitespace removed.
      add autogen.sh script
      coding style cleanups for .h files.
      names.c: fix up some compiler warnings
      coding style cleanups for usbmisc.c
      names.c: fix lots of coding style issues
      devtree.c: coding style cleanups
      lsusb.c: coding style fixes
      lsusb.c: fix some build warnings.
      usb.ids: Reserve EEM Gadget id for the Linux Foundation
      add lsusb.py from Kurt Garloff <garloff@suse.de>

Philip A. Prindeville (1):
      Fix build issue with libusb location



                 reply	other threads:[~2010-03-18  1:51 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=20100318015109.GB28263@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

all inboxes | Powered by JetHome®