)]}'
{
  "log": [
    {
      "commit": "31143a12044caa3521edafd736e3bc18c098d2fd",
      "tree": "b9adfc09908b0a7b6abe041f865cf335eac03056",
      "parents": [
        "fc9c9ab22d5650977c417ef2032d02f455011b23"
      ],
      "author": {
        "name": "Bert Wesarg",
        "email": "wesarg@informatik.uni-halle.de",
        "time": "Sat Apr 16 15:25:42 2005 -0700"
      },
      "committer": {
        "name": "Linus Torvalds",
        "email": "torvalds@ppc970.osdl.org",
        "time": "Sat Apr 16 15:25:42 2005 -0700"
      },
      "message": "[PATCH] kernel/param.c: don\u0027t use .max when .num is NULL in param_array_set()\n\nthere seems to be a bug, at least for me, in kernel/param.c for arrays with\n.num \u003d\u003d NULL.  If .num \u003d\u003d NULL, the function param_array_set() uses \u0026.max\nfor the call to param_array(), wich alters the .max value to the number of\narguments.  The result is, you can\u0027t set more array arguments as the last\ntime you set the parameter.\n\nexample:\n\n# a module \u0027example\u0027 with\n# static int array[10] \u003d { 0, };\n# module_param_array(array, int, NULL, 0644);\n\n$ insmod example.ko array\u003d1,2,3\n$ cat /sys/module/example/parameters/array\n1,2,3\n$ echo \"4,3,2,1\" \u003e /sys/module/example/parameters/array\n$ dmesg | tail -n 1\nkernel: array: can take only 3 arguments\n\nSigned-off-by: Bert Wesarg \u003cwesarg@informatik.uni-halle.de\u003e\nSigned-off-by: Andrew Morton \u003cakpm@osdl.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@osdl.org\u003e\n"
    },
    {
      "commit": "1da177e4c3f41524e886b7f1b8a0c1fc7321cac2",
      "tree": "0bba044c4ce775e45a88a51686b5d9f90697ea9d",
      "parents": [],
      "author": {
        "name": "Linus Torvalds",
        "email": "torvalds@ppc970.osdl.org",
        "time": "Sat Apr 16 15:20:36 2005 -0700"
      },
      "committer": {
        "name": "Linus Torvalds",
        "email": "torvalds@ppc970.osdl.org",
        "time": "Sat Apr 16 15:20:36 2005 -0700"
      },
      "message": "Linux-2.6.12-rc2\n\nInitial git repository build. I\u0027m not bothering with the full history,\neven though we have it. We can create a separate \"historical\" git\narchive of that later if we want to, and in the meantime it\u0027s about\n3.2GB when imported into git - space that would just make the early\ngit days unnecessarily complicated, when we don\u0027t have a lot of good\ninfrastructure for it.\n\nLet it rip!\n"
    }
  ]
}