)]}'
{
  "commit": "c7fc77f78f16d138ca997ce096a62f46e2e9420a",
  "tree": "0478e5dde66f6ff86d4baa0fe541748e1a6f1ed2",
  "parents": [
    "f34217977d717385a3e9fd7018ac39fade3964c0"
  ],
  "author": {
    "name": "Tejun Heo",
    "email": "tj@kernel.org",
    "time": "Fri Jul 02 10:03:51 2010 +0200"
  },
  "committer": {
    "name": "Tejun Heo",
    "email": "tj@kernel.org",
    "time": "Fri Jul 02 11:00:08 2010 +0200"
  },
  "message": "workqueue: remove WQ_SINGLE_CPU and use WQ_UNBOUND instead\n\nWQ_SINGLE_CPU combined with @max_active of 1 is used to achieve full\nordering among works queued to a workqueue.  The same can be achieved\nusing WQ_UNBOUND as unbound workqueues always use the gcwq for\nWORK_CPU_UNBOUND.  As @max_active is always one and benefits from cpu\nlocality isn\u0027t accessible anyway, serving them with unbound workqueues\nshould be fine.\n\nDrop WQ_SINGLE_CPU support and use WQ_UNBOUND instead.  Note that most\nsingle thread workqueue users will be converted to use multithread or\nnon-reentrant instead and only the ones which require strict ordering\nwill keep using WQ_UNBOUND + @max_active of 1.\n\nSigned-off-by: Tejun Heo \u003ctj@kernel.org\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "67ce734747f6979aeeec03587172adbe8416efcb",
      "old_mode": 33188,
      "old_path": "include/linux/workqueue.h",
      "new_id": "d74a529ed13e8926f20288c00f3b299ced328148",
      "new_mode": 33188,
      "new_path": "include/linux/workqueue.h"
    },
    {
      "type": "modify",
      "old_id": "4608563cdd63dd0e2ba6c17f1e7399bfd7548d11",
      "old_mode": 33188,
      "old_path": "kernel/workqueue.c",
      "new_id": "20d6237d7498bf389d5c9a9d95dd728d69c7781b",
      "new_mode": 33188,
      "new_path": "kernel/workqueue.c"
    }
  ]
}