)]}'
{
  "commit": "2a3d4f1f1f839e354ebd7d40b2d5d8ac8481a930",
  "tree": "a22da6bd95c69ab7771b8e7870351bfa15b8025d",
  "parents": [
    "9abcf40b1d1443e6f0ef86e6a822193142a34abc"
  ],
  "author": {
    "name": "Al Viro",
    "email": "viro@ftp.linux.org.uk",
    "time": "Thu Feb 01 13:52:23 2007 +0000"
  },
  "committer": {
    "name": "Linus Torvalds",
    "email": "torvalds@woody.linux-foundation.org",
    "time": "Thu Feb 01 16:17:06 2007 -0800"
  },
  "message": "[PATCH] __crc_... is intended to be absolute\n\ni386 boot/compressed/relocs checks for absolute symbols and warns about\nunexpected ones.  If you build with modversions, you get ~2500 warnings\nabout __crc_\u003csymbol\u003e.  These suckers are really absolute symbols - we\ndo _not_ want to modify them on relocation.\n\nThey are generated by genksyms - EXPORT_... generates a weak alias, then\ngenksyms produces an ld script with __crc_\u003csymbol\u003e \u003d \u003cchecksum\u003e and it\u0027s\nfed to ld to produce the final object file.  Their only use is to match\nkernel and module at modprobe time; they _must_ be absolute.\n\nboot/compressed/relocs has a whitelist of known absolute symbols, but\nit doesn\u0027t know about __crc_... stuff.  As the result, we get shitloads\nof false positives on any ld(1) version.\n\nSigned-off-by: Al Viro \u003cviro@zeniv.linux.org.uk\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "468da89153c470ee2311a30ac445cabd2301755b",
      "old_mode": 33188,
      "old_path": "arch/i386/boot/compressed/relocs.c",
      "new_id": "881951ca03e1cc53be63665b5c717e04adf1d47a",
      "new_mode": 33188,
      "new_path": "arch/i386/boot/compressed/relocs.c"
    }
  ]
}