)]}'
{
  "commit": "5438b79cffb1a78b6cc5808370056ec3c236e363",
  "tree": "f31e09f4eb5bd619ce6f15ef97ccc99c851c9735",
  "parents": [
    "b95c5971ead4174e23837e1b34b3b4428b9fe17e"
  ],
  "author": {
    "name": "Steven Rostedt (Google)",
    "email": "rostedt@goodmis.org",
    "time": "Fri Oct 31 11:55:13 2025 -0400"
  },
  "committer": {
    "name": "Yordan Karadzhov",
    "email": "y.karadz@gmail.com",
    "time": "Thu Jun 04 12:44:40 2026 +0300"
  },
  "message": "Documentation: Update latency description for migration disabled\n\nStarting in 5.11, the Linux kernel implemented a \"migrate disabled\"\ncounter for each task. When the counter is non-zero, the task will be\ntemporarily pinned to its CPU. This is useful for accessing per CPU data\nthat is protected by a per CPU mutex. The task can still be preempted, but\nit must not leave the CPU. When its \"migrate disabled\" counter is greater\nthan zero, it will not migrate.\n\nThe latency field of the tracer now shows this number. Updated the\ndocumentation to explain it.\n\nReported-by: Jorge Merlino \u003cjorge.merlino@canonical.com\u003e\nCloses: https://lore.kernel.org/all/fe35c5eb-7132-4203-9d6f-0a8272b114fa@canonical.com/\nSigned-off-by: Steven Rostedt (Google) \u003crostedt@goodmis.org\u003e\nSigned-off-by: Yordan Karadzhov \u003cy.karadz@gmail.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "7dac810bebbd1f40bbeff9bbfeeafe7c9f0fe3f8",
      "old_mode": 33188,
      "old_path": "Documentation/HTML/index.html",
      "new_id": "281307735289cf0d11233ef6fc9667cfc661fe4a",
      "new_mode": 33188,
      "new_path": "Documentation/HTML/index.html"
    }
  ]
}