)]}'
{
  "commit": "f505e91ef511a20b2bc3d0eaca41faecdb715027",
  "tree": "7610e38b15129e8017dbf60dbd769909da4e0027",
  "parents": [
    "bbbc08a154a1750371f8347a5353819551d11abb"
  ],
  "author": {
    "name": "Alexander Shishkin",
    "email": "alexander.shishkin@linux.intel.com",
    "time": "Thu Jun 27 15:51:47 2019 +0300"
  },
  "committer": {
    "name": "Greg Kroah-Hartman",
    "email": "gregkh@linuxfoundation.org",
    "time": "Wed Jul 03 17:45:57 2019 +0200"
  },
  "message": "intel_th: msu: Start read iterator from a non-empty window\n\nIn multi-window mode, the read iterator is supposed to start from the\nwindow with the oldest data, which is, chronologically, the next window\nafter the one with the newest data. This, however, fails to take into\naccount the potentially empty windows, so in short trace sessions it\u0027s\npossible to have a lot of zeroes read from the character device first.\n\nFix this by skipping over the empty windows in initialization of the\nread iterator.\n\nSigned-off-by: Alexander Shishkin \u003calexander.shishkin@linux.intel.com\u003e\nReviewed-by: Andy Shevchenko \u003candriy.shevchenko@linux.intel.com\u003e\nLink: https://lore.kernel.org/r/20190627125152.54905-5-alexander.shishkin@linux.intel.com\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "aedfd8629e580f76b42cd8a1a604b81d8a0072bf",
      "old_mode": 33188,
      "old_path": "drivers/hwtracing/intel_th/msu.c",
      "new_id": "8ab28e5fb366f62d18168b0d0b8fc305df85cf9c",
      "new_mode": 33188,
      "new_path": "drivers/hwtracing/intel_th/msu.c"
    }
  ]
}