)]}'
{
  "commit": "e6be133b68ae2c8f89d46da25ed7b31b84793e7e",
  "tree": "78ae9a2f10daa5e21c1761039146dffad1377a09",
  "parents": [
    "c2aecda79cd872679b9b11f9e59d797fb4c7d677"
  ],
  "author": {
    "name": "Shashi Rao",
    "email": "shashi@sun.com",
    "time": "Wed Mar 28 15:56:28 2007 -0700"
  },
  "committer": {
    "name": "David Woodhouse",
    "email": "dwmw2@infradead.org",
    "time": "Tue Apr 17 14:11:20 2007 -0400"
  },
  "message": "[MTD] Fix fwh_lock locking\n\nThis is on a custom board with a mapping driver access to an ST\nM50LPW080 chip. This chip is probed successfully with\ndo_map_probe(\"jedec_probe\",...). If I use the mtdchar interface to\nperform unlock-\u003eerase-\u003eprogram-\u003elock on any of the 16 eraseblocks in the\nchip, the chip is left in FL_STATUS mode while the data structures\nbelieve that the chip is in FL_READY mode. Hence, any subsequent reads\nto any flash byte results in 0x80 being read.\n\nSigned-off-by: Shashi Rao \u003cshashi@sun.com\u003e\nSigned-off-by: David Woodhouse \u003cdwmw2@infradead.org\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "77303ce5dcf1699d3097a76a25935d884f515fb3",
      "old_mode": 33188,
      "old_path": "drivers/mtd/chips/fwh_lock.h",
      "new_id": "ab44f2b996f8ceb4f2729fa8fdc7c1956386a1d6",
      "new_mode": 33188,
      "new_path": "drivers/mtd/chips/fwh_lock.h"
    }
  ]
}