)]}'
{
  "commit": "daae2ab46e0cb612f50ca1d86cf50e5962461ae5",
  "tree": "426abd70f44f6b68d58754478c3b30a98488d835",
  "parents": [
    "21f6c39938a10abfc98961000b04b55fa0e70d89"
  ],
  "author": {
    "name": "Dmitry Torokhov",
    "email": "dmitry.torokhov@gmail.com",
    "time": "Sun Aug 30 13:52:52 2026 -0700"
  },
  "committer": {
    "name": "Dmitry Torokhov",
    "email": "dmitry.torokhov@gmail.com",
    "time": "Sun Sep 20 12:52:10 2026 -0700"
  },
  "message": "Input: gscps2 - drop busy-wait and manual interrupt pump on transmit\n\nIn gscps2_writeb_output(), after writing data to GSC_XMTDATA, the driver\nexplicitly executed mdelay(6) and manually called gscps2_interrupt() as a\npolling mechanism to accelerate command responses (such as keyboard ACK\nor LED updates).\n\nOn PA-RISC, the PS/2 controller asserts a level interrupt to the system\nASIC whenever received data arrives in hardware, and the input/serio\nsubsystem handles command responses asynchronously via completions.\nBusy-waiting for 6 ms on every transmitted byte introduces significant\nunnecessary latency during multi-byte command sequences and complicates\ninterrupt handler locking.\n\nRemove mdelay(6) and the manual invocation of gscps2_interrupt() from\ngscps2_writeb_output(), relying on normal hardware interrupt delivery.\n\nReported-by: sashiko-bot@kernel.org\nAssisted-by: LLM\nLink: https://patch.msgid.link/20260830-gscps2-v1-7-c733d4cae7f9@gmail.com\nAcked-by: Helge Deller \u003cdeller@gmx.de\u003e\nTested-by: Helge Deller \u003cdeller@gmx.de\u003e\nSigned-off-by: Dmitry Torokhov \u003cdmitry.torokhov@gmail.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "2afd53a163ffa35add85b49da52149fdc9504480",
      "old_mode": 33188,
      "old_path": "drivers/input/serio/gscps2.c",
      "new_id": "985539f1d0886a2921b1d3f81b159a18dda956a4",
      "new_mode": 33188,
      "new_path": "drivers/input/serio/gscps2.c"
    }
  ]
}