)]}'
{
  "log": [
    {
      "commit": "b9d0a25a484a90c1d60b974d115eff2fe580ce16",
      "tree": "b76924924662ab1867b53001ea4a0db4a87b57ce",
      "parents": [
        "e90b1a2be6010acf01673b0625cfbf18240f7744"
      ],
      "author": {
        "name": "Herbert Xu",
        "email": "herbert@gondor.apana.org.au",
        "time": "Sat Jun 10 18:06:34 2006 +1000"
      },
      "committer": {
        "name": "Herbert Xu",
        "email": "herbert@gondor.apana.org.au",
        "time": "Mon Jun 26 17:34:42 2006 +1000"
      },
      "message": "[CRYPTO] tcrypt: Forbid tcrypt from being built-in\n\nIt makes no sense to build tcrypt into the kernel.  In fact, now that\nthe driver init function\u0027s return status is being checked, it is in\nfact harmful to do so.\n\nSigned-off-by: Herbert Xu \u003cherbert@gondor.apana.org.au\u003e\n"
    },
    {
      "commit": "c8a19c91b5b488fed8cce04200a84c6a35c0bf0c",
      "tree": "e0296c60f7601c5a1d1cf5fa9afd0e38f92e6995",
      "parents": [
        "5cb1454b862ab3040b78364d58330262fea1ddba"
      ],
      "author": {
        "name": "Herbert Xu",
        "email": "herbert@gondor.apana.org.au",
        "time": "Sat Nov 05 18:06:26 2005 +1100"
      },
      "committer": {
        "name": "David S. Miller",
        "email": "davem@sunset.davemloft.net",
        "time": "Mon Jan 09 14:15:39 2006 -0800"
      },
      "message": "[CRYPTO] Allow AES C/ASM implementations to coexist\n\nAs the Crypto API now allows multiple implementations to be registered\nfor the same algorithm, we no longer have to play tricks with Kconfig\nto select the right AES implementation.\n\nThis patch sets the driver name and priority for all the AES\nimplementations and removes the Kconfig conditions on the C implementation\nfor AES.\n\nSigned-off-by: Herbert Xu \u003cherbert@gondor.apana.org.au\u003e\n"
    },
    {
      "commit": "347a8dc3b815f0c0fa62a1df075184ffe4cbdcf1",
      "tree": "a6ec76690127e87fe6efa42b6238caadd6c07e7b",
      "parents": [
        "9bbc8346fb21fad3f678220b067450e436e45dbf"
      ],
      "author": {
        "name": "Martin Schwidefsky",
        "email": "schwidefsky@de.ibm.com",
        "time": "Fri Jan 06 00:19:28 2006 -0800"
      },
      "committer": {
        "name": "Linus Torvalds",
        "email": "torvalds@g5.osdl.org",
        "time": "Fri Jan 06 08:33:53 2006 -0800"
      },
      "message": "[PATCH] s390: cleanup Kconfig\n\nSanitize some s390 Kconfig options.  We have ARCH_S390, ARCH_S390X,\nARCH_S390_31, 64BIT, S390_SUPPORT and COMPAT.  Replace these 6 options by\nS390, 64BIT and COMPAT.\n\nSigned-off-by: Martin Schwidefsky \u003cschwidefsky@de.ibm.com\u003e\nSigned-off-by: Andrew Morton \u003cakpm@osdl.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@osdl.org\u003e\n"
    },
    {
      "commit": "bf754ae8ef8bc443c067601d9401103e4001e7c5",
      "tree": "4241bc75205a638006f40f577e99430099bbe53e",
      "parents": [
        "0a497c17fee428604e06320272ff74415eacdc31"
      ],
      "author": {
        "name": "Jan Glauber",
        "email": "jan.glauber@de.ibm.com",
        "time": "Fri Jan 06 00:19:18 2006 -0800"
      },
      "committer": {
        "name": "Linus Torvalds",
        "email": "torvalds@g5.osdl.org",
        "time": "Fri Jan 06 08:33:50 2006 -0800"
      },
      "message": "[PATCH] s390: aes support\n\nAdd support for the hardware accelerated AES crypto algorithm.\n\nSigned-off-by: Jan Glauber \u003cjan.glauber@de.ibm.com\u003e\nSigned-off-by: Martin Schwidefsky \u003cschwidefsky@de.ibm.com\u003e\nSigned-off-by: Andrew Morton \u003cakpm@osdl.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@osdl.org\u003e\n"
    },
    {
      "commit": "0a497c17fee428604e06320272ff74415eacdc31",
      "tree": "b7ebb455fc908489a783a32f6171a3c36ccdcc4f",
      "parents": [
        "c1e26e1ef7ab50f30e5fbf004fe96ed44321ca78"
      ],
      "author": {
        "name": "Jan Glauber",
        "email": "jan.glauber@de.ibm.com",
        "time": "Fri Jan 06 00:19:18 2006 -0800"
      },
      "committer": {
        "name": "Linus Torvalds",
        "email": "torvalds@g5.osdl.org",
        "time": "Fri Jan 06 08:33:50 2006 -0800"
      },
      "message": "[PATCH] s390: sha256 support\n\nAdd support for the hardware accelerated sha256 crypto algorithm.\n\nSigned-off-by: Jan Glauber \u003cjan.glauber@de.ibm.com\u003e\nSigned-off-by: Martin Schwidefsky \u003cschwidefsky@de.ibm.com\u003e\nSigned-off-by: Andrew Morton \u003cakpm@osdl.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@osdl.org\u003e\n"
    },
    {
      "commit": "c1e26e1ef7ab50f30e5fbf004fe96ed44321ca78",
      "tree": "d4319a9441da5b776637945f9413e702296f5ad3",
      "parents": [
        "d0f4c16febf258ba8c0f917ac3ba935fc5459566"
      ],
      "author": {
        "name": "Jan Glauber",
        "email": "jan.glauber@de.ibm.com",
        "time": "Fri Jan 06 00:19:17 2006 -0800"
      },
      "committer": {
        "name": "Linus Torvalds",
        "email": "torvalds@g5.osdl.org",
        "time": "Fri Jan 06 08:33:50 2006 -0800"
      },
      "message": "[PATCH] s390: in-kernel crypto rename\n\nReplace all references to z990 by s390 in the in-kernel crypto files in\narch/s390/crypto.  The code is not specific to a particular machine (z990) but\nto the s390 platform.  Big diff, does nothing..\n\nSigned-off-by: Jan Glauber \u003cjan.glauber@de.ibm.com\u003e\nSigned-off-by: Martin Schwidefsky \u003cschwidefsky@de.ibm.com\u003e\nSigned-off-by: Andrew Morton \u003cakpm@osdl.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@osdl.org\u003e\n"
    },
    {
      "commit": "fb4f10ed50f01b0f953068456bfb6e2885921b01",
      "tree": "e9eb4112522d7969fdc4bbf6455b6d0d59426121",
      "parents": [
        "75c80c382fbd08acf06fbef9d54c9844e806a8b4"
      ],
      "author": {
        "name": "Aaron Grothe",
        "email": "ajgrothe@yahoo.com",
        "time": "Thu Sep 01 17:42:46 2005 -0700"
      },
      "committer": {
        "name": "David S. Miller",
        "email": "davem@davemloft.net",
        "time": "Thu Sep 01 17:42:46 2005 -0700"
      },
      "message": "[CRYPTO]: Fix XTEA implementation\n\nThe XTEA implementation was incorrect due to a misinterpretation of\noperator precedence.  Because of the wide-spread nature of this\nerror, the erroneous implementation will be kept, albeit under the\nnew name of XETA.\n\nSigned-off-by: Aaron Grothe \u003cajgrothe@yahoo.com\u003e\nSigned-off-by: Herbert Xu \u003cherbert@gondor.apana.org.au\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n"
    },
    {
      "commit": "a2a892a236d03a6e985471a7e57d1c863de144c8",
      "tree": "33b52c87bdecf0f24936b952a565a445ce03c616",
      "parents": [
        "a61cc44812ff94793987bf43b70a3d9bc64a6820"
      ],
      "author": {
        "name": "Andreas Steinmetz",
        "email": "ast@domdv.de",
        "time": "Wed Jul 06 13:55:00 2005 -0700"
      },
      "committer": {
        "name": "David S. Miller",
        "email": "davem@davemloft.net",
        "time": "Wed Jul 06 13:55:00 2005 -0700"
      },
      "message": "[CRYPTO] Add x86_64 asm AES\n\nImplementation:\n\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\nThe encrypt/decrypt code is based on an x86 implementation I did a while\nago which I never published. This unpublished implementation does\ninclude an assembler based key schedule and precomputed tables. For\nsimplicity and best acceptance, however, I took Gladman\u0027s in-kernel code\nfor table generation and key schedule for the kernel port of my\nassembler code and modified this code to produce the key schedule as\nrequired by my assembler implementation. File locations and Kconfig are\nkept similar to the i586 AES assembler implementation.\nIt may seem a little bit strange to use 32 bit I/O and registers in the\nassembler implementation but this gives the best code size. My\nimplementation takes one instruction more per round compared to\nGladman\u0027s x86 assembler but it doesn\u0027t require any stack for local\nvariables or saved registers and it is less serialized than Gladman\u0027s\ncode.\nNote that all comparisons to Gladman\u0027s code were done after my code was\nimplemented. I did only use FIPS PUB 197 for the implementation so my\nimplementation is independent work.\nIf anybody has a better assembler solution for x86_64 I\u0027ll be pleased to\nhave my code replaced with the better solution.\n\nTesting:\n\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\nThe implementation passes the in-kernel crypto testing module and I\u0027m\nrunning it without any problems on my laptop where it is mainly used for\ndm-crypt.\n\nMicrobenchmark:\n\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\nThe microbenchmark was done in userspace with similar compile flags as\nused during kernel compile.\nEncrypt/decrypt is about 35% faster than the generic C implementation.\nAs the generic C as well as my assembler implementation are both table\nI don\u0027t really expect that there is much room for further\nimprovements though I\u0027ll be glad to be corrected here.\nThe key schedule is about 5% slower than the generic C implementation.\nThis is due to the fact that some more work has to be done in the key\nschedule routine to fit the schedule to the assembler implementation.\n\nCode Size:\n\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\nEncrypt and decrypt are together about 2.1 Kbytes smaller than the\ngeneric C implementation which is important with regard to L1 cache\nusage. The key schedule routine is about 100 bytes larger than the\ngeneric C implementation.\n\nData Size:\n\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\nThere\u0027s no difference in data size requirements between the assembler\nimplementation and the generic C implementation.\n\nLicense:\n\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\nGladmans\u0027s code is dual BSD/GPL whereas my assembler code is GPLv2 only\n(I\u0027m  not going to change the license for my code). So I had to change\nthe module license for the x86_64 aes module from \u0027Dual BSD/GPL\u0027 to\n\u0027GPL\u0027 to reflect the most restrictive license within the module.\n\nSigned-off-by: Andreas Steinmetz \u003cast@domdv.de\u003e\nSigned-off-by: Herbert Xu \u003cherbert@gondor.apana.org.au\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n"
    },
    {
      "commit": "c45166be3cc666ce88fe623ad79276c943e74eff",
      "tree": "db59fdfb6834c112c99a5ab8692fe8372d7961ba",
      "parents": [
        "b05d85a87d9711f5f5f2eb05c79038d5d5ff1f44"
      ],
      "author": {
        "name": "Paolo \u0027Blaisorblade\u0027 Giarrusso",
        "email": "blaisorblade@yahoo.it",
        "time": "Sun May 01 08:58:54 2005 -0700"
      },
      "committer": {
        "name": "Linus Torvalds",
        "email": "torvalds@ppc970.osdl.org",
        "time": "Sun May 01 08:58:54 2005 -0700"
      },
      "message": "[PATCH] uml: support AES i586 crypto driver\n\nWe want to make possible, for the user, to enable the i586 AES implementation.\nThis requires a restructure.\n\n- Add a CONFIG_UML_X86 to notify that we are building a UML for i386.\n\n- Rename CONFIG_64_BIT to CONFIG_64BIT as is used for all other archs\n\n- Tell crypto/Kconfig that UML_X86 is as good as X86\n\n- Tell it that it must exclude not X86_64 but 64BIT, which will give the\n  same results.\n\n- Tell kbuild to descend down into arch/i386/crypto/ to build what\u0027s needed.\n\nSigned-off-by: Paolo \u0027Blaisorblade\u0027 Giarrusso \u003cblaisorblade@yahoo.it\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"
    }
  ]
}
