)]}'
{
  "commit": "03ad4a42545591863f3f01be31e15d221cf29c75",
  "tree": "efb04af6d76599817ec93404fe2f48e39592b23e",
  "parents": [
    "211c6ec6011f554a5a9aeacdf0d2c410b343bb2a"
  ],
  "author": {
    "name": "Brian Norris",
    "email": "briannorris@chromium.org",
    "time": "Tue Feb 27 13:01:23 2024 -0800"
  },
  "committer": {
    "name": "Nico Huber",
    "email": "nico.h@gmx.de",
    "time": "Sat Mar 09 13:21:35 2024 +0000"
  },
  "message": "linux_mtd: Provide no-op delay implementation\n\nFlashrom has several magic programmer_delay() calls scattered\nthroughout its codebase (see cli_classic.s/main() and\nflashrom.c/flashrom_image_write(), at least). These delays are\nsuperfluous for the linux_mtd programmer, because it\u0027s an opaque\nprogrammer in which all protocol details are handled by the kernel\ndriver.\n\nStub out the delay function, so we don\u0027t waste up to 1.1 seconds of\nneedless delay time, depending on the operation and CLI vs libflashrom\nusage.\n\nChange-Id: I3ac69d3fd7cfc689c5b32c130d044516ed846c29\nSigned-off-by: Brian Norris \u003cbriannorris@chromium.org\u003e\nReviewed-on: https://review.sourcearcade.org/c/flashprog/+/96\nReviewed-by: Arthur Heymans \u003carthur@aheymans.xyz\u003e\nReviewed-by: Nico Huber \u003cnico.h@gmx.de\u003e\nTested-by: Nico Huber \u003cnico.h@gmx.de\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "e52b8a568cb34dca41c053e27e4113253c5d42ab",
      "old_mode": 33188,
      "old_path": "linux_mtd.c",
      "new_id": "cbc971773d54912da84d04c4d43bd7a979054974",
      "new_mode": 33188,
      "new_path": "linux_mtd.c"
    }
  ]
}