)]}'
{
  "commit": "4fb84c8a65f2da52b43288f86120810e80f93adc",
  "tree": "9596bbccc2dd4015290ef193b06545e10551e7e8",
  "parents": [
    "c88f5062a1fb1d88d07e261e6c58ac743e8a92da"
  ],
  "author": {
    "name": "Nico Huber",
    "email": "nico.h@gmx.de",
    "time": "Sun Jul 21 15:59:57 2024 +0200"
  },
  "committer": {
    "name": "Nico Huber",
    "email": "nico.h@gmx.de",
    "time": "Fri Aug 30 00:53:43 2024 +0200"
  },
  "message": "spi25_statusreg: Prefer volatile status register writes\n\nNow that libflashprog API users can choose whether to target volatile\nor non-volatile status register bits, we turn around the default beha-\nvior if both are supported. This way, we won\u0027t unnecessarily wear sta-\ntus registers in cases where we automatically disable protections.\n\nChange-Id: I92d84e4a140169464e318c7f84690b7665fdb29f\nSigned-off-by: Nico Huber \u003cnico.h@gmx.de\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "8d5e5255bb144ff793bb00f56183b43935f8a884",
      "old_mode": 33188,
      "old_path": "spi25_statusreg.c",
      "new_id": "f7d988b2714991299c7ae1d71e68958457b2b488",
      "new_mode": 33188,
      "new_path": "spi25_statusreg.c"
    }
  ]
}