)]}'
{
  "log": [
    {
      "commit": "8e8ff02c0b61d9b7c15c7996a2eddbedf51a105b",
      "tree": "dde7fcedee5d8720f5cc95da5ed4629fd3369bc8",
      "parents": [
        "efe87d2b822e42975b4da958c9d321cf89bfeb5a"
      ],
      "author": {
        "name": "Hirokazu Takata",
        "email": "takata@linux-m32r.org",
        "time": "Tue Apr 18 22:21:20 2006 -0700"
      },
      "committer": {
        "name": "Linus Torvalds",
        "email": "torvalds@g5.osdl.org",
        "time": "Wed Apr 19 09:13:50 2006 -0700"
      },
      "message": "[PATCH] m32r: Fix pt_regs for !COFNIG_ISA_DSP_LEVEL2 target\n\nThis modification is required to fix debugging function for m32r targets\nwith !CONFIG_ISA_DSP_LEVEL2, by unifying \u0027struct pt_regs\u0027 and \u0027struct\nsigcontext\u0027 size for all M32R ISA.\n\nSome m32r processor core with !CONFIG_ISA_DSP_LEVEL2 configuration has only\nsingle accumulator a0 (ex.  VDEC2 core, M32102 core, etc.), the others with\nCONFIG_ISA_DSP_LEVEL2 has two accumulators, a0 and a1.\n\nThis means there are two variations of thread context.  So far, we reduced\nand changed stackframe size at a syscall for their context size.  However,\nthis causes a problem that a GDB for processors with CONFIG_ISA_DSP_LEVEL2\ncannot be used for processors with !CONFIG_ISA_DSP_LEVEL2.\n\nFrom the viewpoint of GDB support, we should reduce such variation of\nstackframe size for simplicity.\n\nIn this patch, dummy members are added to \u0027struct pt_regs\u0027 and \u0027struct\nsigcontext\u0027 to adjust their size for !CONFIG_ISA_DSP_LEVEL2.\n\nThis modification is also a one step for a GDB update in future.\nCurrently, on the m32r, GDB can access process\u0027s context by using ptrace\nfunctions in a simple way of register by register access.  By unifying\nstackframe size, we have a possibility to make use of ptrace functions of\nnot only a single register access but also block register access,\nPTRACE_{GETREGS,PUTREGS}.\n\nHowever, for this purpose, we might have to modify stackframe structure\nsome more; for example, PSW (processor status word) register should be\npre-processed before pushing to stack at a syscall, and so on.  In this\ncase, we must update carefully both kernel and GDB at a time...\n\nSigned-off-by: Hayato Fujiwara \u003cfujiwara@linux-m32r.org\u003e\nSigned-off-by: Hirokazu Takata \u003ctakata@linux-m32r.org\u003e\nCc: Kei Sakamoto \u003cksakamot@linux-m32r.org\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"
    }
  ]
}