)]}'
{
  "commit": "1a06e0fe96526e43bab90fbab2263b55fb3d45d1",
  "tree": "14987db825941f75ddf2e2bff6ac434f9e4fb5d4",
  "parents": [
    "8fa336d889caa72637e0860f53fa40ef66dcceaf"
  ],
  "author": {
    "name": "Guennadi Liakhovetski",
    "email": "g.liakhovetski@gmx.de",
    "time": "Thu May 17 18:56:32 2007 +1000"
  },
  "committer": {
    "name": "Paul Mackerras",
    "email": "paulus@samba.org",
    "time": "Mon Jun 25 16:58:07 2007 +1000"
  },
  "message": "[POWERPC] Don\u0027t link timer.o for powerpc systems using generic rtc\n\nWith both generic rtc and powerpc timer suspend / resume code now in the\n(powerpc.git) tree, powerpc platforms using the generic timer and enabling\npower management will have timer.o linked in the kernel, which they don\u0027t\nneed. Moreover, it will likely WARN_ON(!ppc_md.get_rtc_time), save\nzero-time and return no error on suspend...\n\nAs a possible solution we can choose not to build timer.o when RTC_CLASS\nis enabled.  However, I can imagine systems with 2 rtc\u0027s, one served by the\nppc-rtc, another one generic built as a module, in which case using the\nppc-rtc for suspend / resume will be impossible.  Not to say, that such a\nconfiguration would be ugly...\n\nSigned-off-by: G. Liakhovetski \u003cg.liakhovetski@gmx.de\u003e\nSigned-off-by: Paul Mackerras \u003cpaulus@samba.org\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "c3ce0bd12c0b94e461219dca62d3fef5a7650ad9",
      "old_mode": 33188,
      "old_path": "arch/powerpc/sysdev/Makefile",
      "new_id": "31da3b3dc993141fe2d8249f9c7d39eac2a3d4eb",
      "new_mode": 33188,
      "new_path": "arch/powerpc/sysdev/Makefile"
    }
  ]
}