)]}'
{
  "commit": "090b767e97fcdabe8ecd71cf43e7d39d94e6cfef",
  "tree": "68cbae5a009f06c5fbcd91f29d85856967fbb5d9",
  "parents": [
    "d3200be6c423afa1c34f7e39e9f6d04dd5b0af9d"
  ],
  "author": {
    "name": "Christian König",
    "email": "christian.koenig@amd.com",
    "time": "Fri Jul 08 10:21:02 2016 +0200"
  },
  "committer": {
    "name": "Alex Deucher",
    "email": "alexander.deucher@amd.com",
    "time": "Thu Jul 14 16:46:07 2016 -0400"
  },
  "message": "drm/amdgpu: check flush fence context instead of same ring v2\n\nOtherwise we can run into the following situation:\n\n1. Process A grabs ID 1 for ring 0.\n2. Process B grabs ID 1 for ring 0.\n3. Process A grabs ID 1 for ring 1.\n4. Process A tries to reuse ID1 for ring 0 but things he doesn\u0027t need to flush.\n\nv2: check the context of the flush fence instead of messing with the owner field.\n\nSigned-off-by: Christian König \u003cchristian.koenig@amd.com\u003e\nReviewed-by: Alex Deucher \u003calexander.deucher@amd.com\u003e\nReviewed-by: Chunming Zhou \u003cdavid1.zhou@amd.com\u003e\nSigned-off-by: Alex Deucher \u003calexander.deucher@amd.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "2f8496d48c94d9d8a632795c7cca78b5517fd16d",
      "old_mode": 33188,
      "old_path": "drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c",
      "new_id": "a041168ad521842694743c03525123760ed09851",
      "new_mode": 33188,
      "new_path": "drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c"
    }
  ]
}