)]}'
{
  "commit": "06300b21f4c79fd1578f4b7ca4b314fbab61a383",
  "tree": "9b9506e34286f0333ed747c47ec03fd5559f5b71",
  "parents": [
    "bd71c2b17468a2531fb4c81ec1d73520845e97e1"
  ],
  "author": {
    "name": "Sam Ravnborg",
    "email": "sam@mars.ravnborg.org",
    "time": "Wed Jan 25 07:13:18 2006 +0100"
  },
  "committer": {
    "name": "Sam Ravnborg",
    "email": "sam@mars.ravnborg.org",
    "time": "Sun Feb 19 09:51:17 2006 +0100"
  },
  "message": "kbuild: support building individual files for external modules\n\nSupport building individual files when dealing with separate modules.\nSo say you have a module named \"foo\" which consist of two .o files bar.o\nand fun.o.\n\nYou can then do:\nmake -C $KERNELSRC M\u003d`pwd` bar.o\nmake -C $KERNELSRC M\u003d`pwd` bar.lst\nmake -C $KERNELSRC M\u003d`pwd` bar.i\nmake -C $KERNELSRC M\u003d`pwd` /            \u003c\u003d will build all .o files\n                                           and link foo.o\nmake -C $KERNELSRC M\u003d`pwd` foo.ko       \u003c\u003d will build the module\n                                           and do the modpost step\n\t\t\t\t\t   to create foo.ko\n\nThe above will also work if the external module is placed in a\nsubdirectory using a hirachy of kbuild files.\nThanks to Andreas Gruenbacher \u003cagruen@suse.de\u003e for initial feature\nrequest / bug report.\n\nSigned-off-by: Sam Ravnborg \u003csam@ravnborg.org\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "7e77f93634ea507569e3554434fe7978767d7fba",
      "old_mode": 33188,
      "old_path": "Documentation/kbuild/modules.txt",
      "new_id": "87d858df4e3479bfd85b0be27f1f4b5c73a8c78a",
      "new_mode": 33188,
      "new_path": "Documentation/kbuild/modules.txt"
    },
    {
      "type": "modify",
      "old_id": "77a448c8e77654594495d78639e71fd303e35f4f",
      "old_mode": 33188,
      "old_path": "Makefile",
      "new_id": "639d8a48bbde5e246ff43fc3ab87a71ca771d38d",
      "new_mode": 33188,
      "new_path": "Makefile"
    }
  ]
}