)]}'
{
  "commit": "ed45819f315b5a8844b5bfce881a18e9f3a055e7",
  "tree": "dc843958848ed8126ec17e35c5d784f5ef4b6702",
  "parents": [
    "f6f7b52e2f6149d2ee365717afff315b05720162"
  ],
  "author": {
    "name": "Artem Bityutskiy",
    "email": "Artem.Bityutskiy@nokia.com",
    "time": "Wed Nov 12 10:14:10 2008 +0200"
  },
  "committer": {
    "name": "Artem Bityutskiy",
    "email": "Artem.Bityutskiy@nokia.com",
    "time": "Wed Dec 03 13:24:48 2008 +0200"
  },
  "message": "UBI: fix warnings when debugging is enabled\n\nThe \u0027ubi_io_read_vid_hdr()\u0027 and \u0027ubi_io_read_ec_hdr()\u0027 function\nhave the \u0027verbose\u0027 argument which controls whether they should\nprint a warning if the VID/EC header was not found or was corrupted.\nSome callers require the headers to be OK, and pass 1. Some allow\na corrupted/not present header, and pass 0.\n\n       if (UBI_IO_DEBUG)\n               verbose \u003d 1;\n\nAnd UBI_IO_DEBUG is 1 if CONFIG_MTD_UBI_DEBUG_MSG_BLD is true. So in\nthis case the warning is printed all the time. This confuses people.\n\nThus, do not print the messages as warnings if UBI_IO_DEBUG is true,\nbut print them as debugging messages instead.\n\nSigned-off-by: Artem Bityutskiy \u003cArtem.Bityutskiy@nokia.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "2fb64be44f1bab1efde6fd48988b8b22dabd5f39",
      "old_mode": 33188,
      "old_path": "drivers/mtd/ubi/io.c",
      "new_id": "f60f700256f60cba23d7617bc222f9137a9759ed",
      "new_mode": 33188,
      "new_path": "drivers/mtd/ubi/io.c"
    }
  ]
}