)]}'
{
  "commit": "a7e68834fc273930c17e3decaddc13acb87a7dce",
  "tree": "010ed62d3b24099960ff5f52e0e79562ec2a6f20",
  "parents": [
    "491ed06f334955578f0c43d298c46ea1a7ea9e1b"
  ],
  "author": {
    "name": "Brian Norris",
    "email": "computersforpeace@gmail.com",
    "time": "Fri Jun 22 16:35:45 2012 -0700"
  },
  "committer": {
    "name": "David Woodhouse",
    "email": "David.Woodhouse@intel.com",
    "time": "Sat Sep 29 14:51:55 2012 +0100"
  },
  "message": "mtd: nand: use ECC, if present, when scanning OOB\n\nscan_read_raw_oob() is used in only in places where the MTD_OPS_PLACE_OOB mode\nis preferable to MTD_OPS_RAW mode, so use MTD_OPS_PLACE_OOB instead.\nMTD_OPS_PLACE_OOB provides the same functionality with the potential[1] added\nbonus of error correction.\n\nThis brings scan_block_full() in line with scan_block_fast() so that they\nboth read bad block markers with MTD_OPS_PLACE_OOB. This can help in\npreventing 0xff markers (in good blocks) from being interpreted as bad\nblock indicators in the presence of a single bitflip.\n\nNote that ECC error codes (EUCLEAN or EBADMSG) are already silently\nignored in all users of scan_read_raw_oob().\n\n[1] Few  drivers perform proper error correction on OOB data. In those\n    cases, the use of MTD_OPS_RAW vs. MTD_OPS_PLACE_OOB is not\n    significant.\n\nSigned-off-by: Brian Norris \u003ccomputersforpeace@gmail.com\u003e\nSigned-off-by: Artem Bityutskiy \u003cartem.bityutskiy@linux.intel.com\u003e\nSigned-off-by: David Woodhouse \u003cDavid.Woodhouse@intel.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "f5839f06cece60db9ce08228b37080e7182961b7",
      "old_mode": 33188,
      "old_path": "drivers/mtd/nand/nand_bbt.c",
      "new_id": "0e928f3efaa4589b5dcc93efc0e5fc91da6fb84e",
      "new_mode": 33188,
      "new_path": "drivers/mtd/nand/nand_bbt.c"
    }
  ]
}