Fix lsusb -t potentially not listing all devices

There's a bug in the path-parsing code of add_usb_device(). It never checks for
a NULL terminator. This causes some devices to have a bogus
portnum/parent_portnum which in turn makes them not show in the device tree.

Here are two real-world test-cases (yes, the \0 is intentional):
Shows up: add_usb_device("1-1.5.1.4.1\0\n\241M")
Disappers: add_usb_device("1-1.5.1.4.2\0\n0c")
Merge pull request #18 from jethrogb/master

Fix lsusb -t potentially not listing all devices
lsusb: Fix bug in USB 2.0 extended caps descriptor.

The upper bits of the USB 2.0 extended capability BOS descriptor weren't
being shifted into the right byte position.  That didn't matter much
before now, but some USB 2.1 devices will soon have a modified BOS
descriptor that has BESL values in those upper bits.

Signed-off-by: Sarah Sharp <sarah.a.sharp@linux.intel.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
usb-devices: correctly quote driver path

Some drivers have a name containing spaces. This causes quoting issues:

  + '[' -L /sys/bus/usb/devices/usb1/1-1/1-1.4/1-1.4.1/1-1.4.1:1.0/driver ']'
  ++ readlink /sys/bus/usb/devices/usb1/1-1/1-1.4/1-1.4.1/1-1.4.1:1.0/driver
  + driver='../../../../../../../../bus/usb/drivers/MOSCHIP usb-ethernet driver'
  ++ basename ../../../../../../../../bus/usb/drivers/MOSCHIP usb-ethernet driver
  basename: extra operand `driver'
  Try `basename --help' for more information.
  + driver=

Reported-by: Vincent Smeets <Vincent.VSmeets@GMail.com>
Signed-off-by: Aurelien Jarno <aurelien@aurel32.net>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
usb.ids update
usb.ids add BlueZ Host stack device id.

Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
usbutils 007 release