)]}'
{
  "commit": "dfacd68e495bb324ad6e92f4dfcf479dd447c8d3",
  "tree": "d2b75bf431e74349f4878e833dd340ac3ac0036f",
  "parents": [
    "ae9458d6a0956aa21cb49e1251e35a8d4dacbe6e"
  ],
  "author": {
    "name": "Paul Mundt",
    "email": "lethal@linux-sh.org",
    "time": "Thu Jan 31 18:12:34 2008 +0900"
  },
  "committer": {
    "name": "Greg Kroah-Hartman",
    "email": "gregkh@suse.de",
    "time": "Sat Feb 02 15:14:46 2008 -0800"
  },
  "message": "kobject: Always build in kernel/ksysfs.o.\n\nkernel/ksysfs.c seems to be a random dumping group for misc globals\nthat the rest of the tree depend on. This has caused problems with\nexports in the past when sysfs is disabled, which can already be\nobserved in commit-id 51107301b629640f9ab76fe23bf385e187b9ac29.\n\nThe latest one is the kernel_kobj usage, which presently results in:\n\nfs/built-in.o: In function `debugfs_init\u0027:\ninode.c:(.init.text+0xc34): undefined reference to `kernel_kobj\u0027\nmake: *** [.tmp_vmlinux1] Error 1\n\nkernel/ksysfs.c itself at this point only contains globals and some\nbasic sysfs initialization, the sysfs initialization code is optimized\nout when we build with sysfs disabled. Given that, it\u0027s easier to just\nbuild in unconditionally, rather than trying to find some other random\nplace to dump and initialize the globals.\n\nAdditionally, the current trend seems to be decoupling of kobjects from\nsysfs, in which case it still makes sense to perform the kernel_kobj\ninitialization that happens here even if sysfs is disabled, as\nlib/kobject.o is built-in unconditionally.\n\nSigned-off-by: Paul Mundt \u003clethal@linux-sh.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@suse.de\u003e\n\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "8885627ea02138d58901d6c7d5d1cbda07883ccb",
      "old_mode": 33188,
      "old_path": "kernel/Makefile",
      "new_id": "db9af707ff5bbf828174381cf64c65684978bf53",
      "new_mode": 33188,
      "new_path": "kernel/Makefile"
    }
  ]
}