)]}'
{
  "commit": "041e4575f03400e045f00a823fcbbbb337de8409",
  "tree": "3fa062bee497a7ff13d908bf2204de4ec04888da",
  "parents": [
    "d6137badeff1ef64b4e0092ec249ebdeaeb3ff37"
  ],
  "author": {
    "name": "Brian Norris",
    "email": "computersforpeace@gmail.com",
    "time": "Thu Jun 23 16:45:24 2011 -0700"
  },
  "committer": {
    "name": "Artem Bityutskiy",
    "email": "artem.bityutskiy@intel.com",
    "time": "Sun Sep 11 15:02:14 2011 +0300"
  },
  "message": "mtd: nand: handle ECC errors in OOB\n\nWhile the standard NAND OOB functions do not do ECC on the spare area,\nit is possible for a driver to supply its own OOB ECC functions (e.g., HW\nECC). nand_do_read_oob should act like nand_do_read_ops in checking the\nECC stats and returning -EBADMSG or -EUCLEAN on uncorrectable errors or\ncorrectable bitflips, respectively. These error codes could be used in\nflash-based BBT code or in YAFFS, for example.\n\nDoing this, however, messes with the behavior of mtd_do_readoob. Now,\nmtd_do_readoob should check whether we had -EUCLEAN or -EBADMSG errors\nand discard those as \"non-fatal\" so that the ioctls can still succeed\nwith (possibly uncorrected) data.\n\nSigned-off-by: Brian Norris \u003ccomputersforpeace@gmail.com\u003e\nSigned-off-by: Artem Bityutskiy \u003cArtem.Bityutskiy@nokia.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "c60067b1f07ae5c6b82ee557fd219d8c81bd4fe7",
      "old_mode": 33188,
      "old_path": "drivers/mtd/mtdchar.c",
      "new_id": "d5924635ead500e2bda6a5a3ed15434e22418425",
      "new_mode": 33188,
      "new_path": "drivers/mtd/mtdchar.c"
    },
    {
      "type": "modify",
      "old_id": "237d7daa189c64de451a743caee827bca67ef544",
      "old_mode": 33188,
      "old_path": "drivers/mtd/nand/nand_base.c",
      "new_id": "5418d27122c4775e4f531f2c18d449882e3a8661",
      "new_mode": 33188,
      "new_path": "drivers/mtd/nand/nand_base.c"
    }
  ]
}