)]}'
{
  "log": [
    {
      "commit": "033b8ffe3f1ea8174d51d125838ac6deea60f63f",
      "tree": "c74af61a3f9c68e15ff858ac0bccc07a2fbbdbd4",
      "parents": [
        "84aa462e2c2cd1b921f6b8e283f8d41666e02e8e"
      ],
      "author": {
        "name": "Mike Westerhof",
        "email": "mwester@dls.net",
        "time": "Thu Oct 11 03:18:14 2007 +0100"
      },
      "committer": {
        "name": "Russell King",
        "email": "rmk+kernel@arm.linux.org.uk",
        "time": "Fri Oct 12 23:43:48 2007 +0100"
      },
      "message": "[ARM] 4599/1: Preserve ATAG list for use with kexec (2.6.23)\n\nThis patch resolves a kexec boot failure that can occur because\nno ATAGs are passed in to the kexec\u0027d kernel. Currently the\nnewly-kexec\u0027d kernel may fail if it requires specific ATAGs, or\nit may fail because the fixed memory location at which it expects\nto find the ATAGs may contain random data instead of ATAGs.\n\nThe patch ensures that any ATAGs passed to the current kernel\nat boot time are copied to a static buffer, and are copied back\nwhen kexec copies the new kernel into place. Thus the new\nkernel sees the same ATAGs from kexec and the boot loader.\n\nThe boot parameters are copied without regard to type, content,\nor length -- this patch\u0027s scope is limited soley to saving and\nrestoring a fixed-size block of memory containing the kernel\u0027s\nboot parameters. Additional functionality to examine, alter, or\nreplace the ATAGs (using kexec, for example) can be implemented\nby manipulating the static buffer containing the preserved ATAGs.\n\nNote: the size of the buffer (1.5KB) is selected to comfortably\nhold one of each ATAG type, including a maximum-length command\nline and the maximum number of ATAG_MEM structures currently\nsupported by the kernel. Should an ATAG list exceed that limit,\nthe list will be silently truncated to that limit (to do other-\nwise at that point in the boot process would make a simple\nproblem exceedingly complicated).\n\n[Note: this is the same patch as 4579, modified to accomodate\nthe ATAG changes introduced in 2.6.23]\n\nSigned-off-by: Mike Westerhof \u003cmwester at dls.net\u003e\nSigned-off-by: Russell King \u003crmk+kernel@arm.linux.org.uk\u003e\n"
    },
    {
      "commit": "6672f76a5a1878d42264c1deba8f1ab52b4618d9",
      "tree": "77396eefed3548183c1f0c3d1dc38f034d8fc429",
      "parents": [
        "73285082745045bcd64333c1fbaa88f8490f2626"
      ],
      "author": {
        "name": "Simon Horman",
        "email": "horms@verge.net.au",
        "time": "Tue May 08 00:28:22 2007 -0700"
      },
      "committer": {
        "name": "Linus Torvalds",
        "email": "torvalds@woody.linux-foundation.org",
        "time": "Tue May 08 11:15:07 2007 -0700"
      },
      "message": "kdump/kexec: calculate note size at compile time\n\nCurrently the size of the per-cpu region reserved to save crash notes is\nset by the per-architecture value MAX_NOTE_BYTES.  Which in turn is\ncurrently set to 1024 on all supported architectures.\n\nWhile testing ia64 I recently discovered that this value is in fact too\nsmall.  The particular setup I was using actually needs 1172 bytes.  This\nlead to very tedious failure mode where the tail of one elf note would\noverwrite the head of another if they ended up being alocated sequentially\nby kmalloc, which was often the case.\n\nIt seems to me that a far better approach is to caclculate the size that\nthe area needs to be.  This patch does just that.\n\nIf a simpler stop-gap patch for ia64 to be squeezed into 2.6.21(.X) is\nneeded then this should be as easy as making MAX_NOTE_BYTES larger in\narch/asm-ia64/kexec.h.  Perhaps 2048 would be a good choice.  However, I\nthink that the approach in this patch is a much more robust idea.\n\nAcked-by:  Vivek Goyal \u003cvgoyal@in.ibm.com\u003e\nSigned-off-by: Simon Horman \u003chorms@verge.net.au\u003e\nSigned-off-by: Andrew Morton \u003cakpm@linux-foundation.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\n"
    },
    {
      "commit": "c587e4a6a4d808fd2a1c4e7fb2d5a3a31e300d23",
      "tree": "77af76e34786ad795e5df625915fc58bca1a9abc",
      "parents": [
        "3b581f5485c180016a6c36c4c7007e21c53f8a63"
      ],
      "author": {
        "name": "Richard Purdie",
        "email": "rpurdie@rpsys.net",
        "time": "Tue Feb 06 21:29:00 2007 +0100"
      },
      "committer": {
        "name": "Russell King",
        "email": "rmk+kernel@arm.linux.org.uk",
        "time": "Fri Feb 16 14:37:06 2007 +0000"
      },
      "message": "[ARM] 4137/1: Add kexec support\n\nAdd kexec support to ARM.\n\nImprovements like commandline handling could be made but this patch gives\nbasic functional support. It uses the next available syscall number, 347.\n\nOnce the syscall number is known, userspace support will be\nfinalised/submitted to kexec-tools, various patches already exist.\n\nOriginally based on a patch by Maxim Syrchin but updated and forward\nported by various people.\n\nSigned-off-by: Richard Purdie \u003crpurdie@rpsys.net\u003e\nSigned-off-by: Russell King \u003crmk+kernel@arm.linux.org.uk\u003e\n"
    }
  ]
}