)]}'
{
  "log": [
    {
      "commit": "3af5b90bde5000abc739996cb03fd718e753d053",
      "tree": "579ab3154c56dfa49e83acb463f04daed8135988",
      "parents": [
        "7dc748e4e720c1a98185363096ad7582e9113092"
      ],
      "author": {
        "name": "Kamalesh Babulal",
        "email": "kamalesh@linux.vnet.ibm.com",
        "time": "Sat Apr 05 21:00:57 2008 +0800"
      },
      "committer": {
        "name": "Herbert Xu",
        "email": "herbert@gondor.apana.org.au",
        "time": "Mon Apr 21 10:19:34 2008 +0800"
      },
      "message": "[CRYPTO] all: Clean up init()/fini()\n\nOn Thu, Mar 27, 2008 at 03:40:36PM +0100, Bodo Eggert wrote:\n\u003e Kamalesh Babulal \u003ckamalesh@linux.vnet.ibm.com\u003e wrote:\n\u003e \n\u003e \u003e This patch cleanups the crypto code, replaces the init() and fini()\n\u003e \u003e with the \u003calgorithm name\u003e_init/_fini\n\u003e \n\u003e This part ist OK.\n\u003e \n\u003e \u003e or init/fini_\u003calgorithm name\u003e (if the \n\u003e \u003e \u003calgorithm name\u003e_init/_fini exist)\n\u003e \n\u003e Having init_foo and foo_init won\u0027t be a good thing, will it? I\u0027d start\n\u003e confusing them.\n\u003e \n\u003e What about foo_modinit instead?\n\nThanks for the suggestion, the init() is replaced with\n\n\t\u003calgorithm name\u003e_mod_init ()\n\nand fini () is replaced with \u003calgorithm name\u003e_mod_fini.\n \nSigned-off-by: Kamalesh Babulal \u003ckamalesh@linux.vnet.ibm.com\u003e\nSigned-off-by: Herbert Xu \u003cherbert@gondor.apana.org.au\u003e\n"
    },
    {
      "commit": "eb6f13eb9f812f5812ed5d14f241309da369dee6",
      "tree": "eb49b8f64333e9389852dcd99a38279a076150d6",
      "parents": [
        "7f6813786a6521380e1756ca5b4336bc63c5bf7d"
      ],
      "author": {
        "name": "Tan Swee Heng",
        "email": "thesweeheng@gmail.com",
        "time": "Fri Dec 07 16:38:45 2007 +0800"
      },
      "committer": {
        "name": "Herbert Xu",
        "email": "herbert@gondor.apana.org.au",
        "time": "Fri Jan 11 08:16:34 2008 +1100"
      },
      "message": "[CRYPTO] salsa20_generic: Fix multi-page processing\n\nThis patch fixes the multi-page processing bug that affects large test\nvectors (the same bug that previously affected ctr.c).\n\nThere is an optimization for the case walk.nbytes \u003d\u003d nbytes. Also we\nnow use crypto_xor() instead of adhoc XOR routines.\n\nSigned-off-by: Tan Swee Heng \u003cthesweeheng@gmail.com\u003e\nSigned-off-by: Herbert Xu \u003cherbert@gondor.apana.org.au\u003e\n"
    },
    {
      "commit": "2407d60872dd2a95404c6048f775f3b64d438f4b",
      "tree": "6a333c5eaae616736b2f184cee8e9f052cee966d",
      "parents": [
        "332f8840f7095d294f9bb066b175a100bcde214c"
      ],
      "author": {
        "name": "Tan Swee Heng",
        "email": "thesweeheng@gmail.com",
        "time": "Fri Nov 23 19:45:00 2007 +0800"
      },
      "committer": {
        "name": "Herbert Xu",
        "email": "herbert@gondor.apana.org.au",
        "time": "Fri Jan 11 08:16:15 2008 +1100"
      },
      "message": "[CRYPTO] salsa20: Salsa20 stream cipher\n\nThis patch implements the Salsa20 stream cipher using the blkcipher interface.\n\nThe core cipher code comes from Daniel Bernstein\u0027s submission to eSTREAM:\n  http://www.ecrypt.eu.org/stream/svn/viewcvs.cgi/ecrypt/trunk/submissions/salsa20/full/ref/\n\nThe test vectors comes from:\n  http://www.ecrypt.eu.org/stream/svn/viewcvs.cgi/ecrypt/trunk/submissions/salsa20/full/\n\nIt has been tested successfully with \"modprobe tcrypt mode\u003d34\" on an\nUML instance.\n\nSigned-off-by: Tan Swee Heng \u003cthesweeheng@gmail.com\u003e\nSigned-off-by: Herbert Xu \u003cherbert@gondor.apana.org.au\u003e\n"
    }
  ]
}