)]}'
{
  "commit": "c43831fb47e4ee51967870c7b5deb08789b0874c",
  "tree": "148a7edf64a65a4a9b89ebe79df246ae775bc4a6",
  "parents": [
    "ed3a328db9d9a027092edc2c17348068e3271cef"
  ],
  "author": {
    "name": "Hans de Goede",
    "email": "hdegoede@redhat.com",
    "time": "Wed Nov 24 12:57:59 2010 +0100"
  },
  "committer": {
    "name": "Gerd Hoffmann",
    "email": "kraxel@redhat.com",
    "time": "Wed May 04 12:25:24 2011 +0200"
  },
  "message": "usb-linux: Get the alt. setting from sysfs rather then asking the dev\n\nAt least one device I have lies when receiving a USB_REQ_GET_INTERFACE,\nalways returning 0 even if the alternate setting is different. This is\nlikely caused because in practice this control message is never used as\nthe operating system\u0027s usb stack knows which alternate setting it has\ntold the device to get into, and thus this ctrl message does not get\ntested by device manufacturers.\n\nWhen usb_fs_type \u003d\u003d USB_FS_SYS, the active alt. setting can be read directly\nfrom sysfs, which allows using this device through qemu\u0027s usb redirection.\nMore in general it seems a good idea to not send needless control msg\u0027s to\ndevices, esp. as the code in question is called every time a set_interface\nis done. Which happens multiple times during virtual machine startup, and\nwhen device drivers are activating the usb device.\n\nSigned-off-by: Hans de Goede \u003chdegoede@redhat.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "353e1b1232764550f2cb640a3d913385907c944e",
      "old_mode": 33188,
      "old_path": "usb-linux.c",
      "new_id": "f4601e6e63d34c8e63e738e76cfea97725e4a32a",
      "new_mode": 33188,
      "new_path": "usb-linux.c"
    }
  ]
}