)]}'
{
  "commit": "a72188d8a64ebe74722f1cf7ffac41b41ffdba21",
  "tree": "5283404345b270bf5ca95ce8d792baacdf8cf7dc",
  "parents": [
    "8dac456a681bd94272ff50ecb31be6b669382c2b"
  ],
  "author": {
    "name": "Darren Hart",
    "email": "dvhltc@us.ibm.com",
    "time": "Fri Apr 03 13:40:22 2009 -0700"
  },
  "committer": {
    "name": "Thomas Gleixner",
    "email": "tglx@linutronix.de",
    "time": "Mon Apr 06 11:14:02 2009 +0200"
  },
  "message": "futex: add FUTEX_HAS_TIMEOUT flag to restart.futex.flags\n\nCurrently restart is only used if there is a timeout. The requeue_pi\nfunctionality requires restarting to futex_lock_pi() on signal after\nwakeup in futex_wait_requeue_pi() regardless of if there was a timeout\nor not. Using 0 for the timeout value is confusing as that could\nindicate an expired timer. The flag makes this explicit. While the\ncheck is not technically needed in futex_wait_restart(), doing so\nmakes the code consistent with and will avoid confusion should the\nneed arise to restart wait without a timeout.\n\nSigned-off-by: Darren Hart \u003cdvhltc@us.ibm.com\u003e\nReviewed-by: Thomas Gleixner \u003ctglx@linutronix.de\u003e\nSigned-off-by: Thomas Gleixner \u003ctglx@linutronix.de\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "af831fbb7fb43e4d44fdbde2d53faf45fec8ede8",
      "old_mode": 33188,
      "old_path": "kernel/futex.c",
      "new_id": "6b597cf33b02f4a03b269547b88ae4f8428aab54",
      "new_mode": 33188,
      "new_path": "kernel/futex.c"
    }
  ]
}