)]}'
{
  "log": [
    {
      "commit": "e853c3cfa8cc24869ecd2526e589bcb176bc12e9",
      "tree": "24ad223420bdea868e891676ebb7285e3c477a05",
      "parents": [
        "8f21cf0d2bae04ece761595036c9da8328b279aa"
      ],
      "author": {
        "name": "Herbert Xu",
        "email": "herbert@gondor.apana.org.au",
        "time": "Tue Aug 22 00:06:54 2006 +1000"
      },
      "committer": {
        "name": "Herbert Xu",
        "email": "herbert@gondor.apana.org.au",
        "time": "Thu Sep 21 11:41:51 2006 +1000"
      },
      "message": "[CRYPTO] api: Added crypto_type support\n\nThis patch adds the crypto_type structure which will be used for all new\ncrypto algorithm types, beginning with block ciphers.\n\nThe primary purpose of this abstraction is to allow different crypto_type\nobjects for crypto algorithms of the same type, in particular, there will\nbe a different crypto_type objects for asynchronous algorithms.\n\nSigned-off-by: Herbert Xu \u003cherbert@gondor.apana.org.au\u003e\n"
    },
    {
      "commit": "cce9e06d100df19a327b19f23adad76e7bf63edd",
      "tree": "ce10f50679db9ed8db92912c104eef1f05efc3c5",
      "parents": [
        "9409f38a0c8773c04bff8dda8c552d7ea013d956"
      ],
      "author": {
        "name": "Herbert Xu",
        "email": "herbert@gondor.apana.org.au",
        "time": "Mon Aug 21 21:08:13 2006 +1000"
      },
      "committer": {
        "name": "Herbert Xu",
        "email": "herbert@gondor.apana.org.au",
        "time": "Thu Sep 21 11:16:30 2006 +1000"
      },
      "message": "[CRYPTO] api: Split out low-level API\n\nThe crypto API is made up of the part facing users such as IPsec and the\nlow-level part which is used by cryptographic entities such as algorithms.\nThis patch splits out the latter so that the two APIs are more clearly\ndelineated.  As a bonus the low-level API can now be modularised if all\nalgorithms are built as modules.\n\nSigned-off-by: Herbert Xu \u003cherbert@gondor.apana.org.au\u003e\n"
    },
    {
      "commit": "6521f30273fbec65146a0f16de74b7b402b0f7b0",
      "tree": "1e664f6c1a7c960c60c4cae01585933029f81a5f",
      "parents": [
        "72fa491912689ca69dd15f4266945d2c2f2819f8"
      ],
      "author": {
        "name": "Herbert Xu",
        "email": "herbert@gondor.apana.org.au",
        "time": "Sun Aug 06 20:28:44 2006 +1000"
      },
      "committer": {
        "name": "Herbert Xu",
        "email": "herbert@gondor.apana.org.au",
        "time": "Thu Sep 21 11:16:29 2006 +1000"
      },
      "message": "[CRYPTO] api: Add crypto_alg reference counting\n\nUp until now we\u0027ve relied on module reference counting to ensure that the\ncrypto_alg structures don\u0027t disappear from under us.  This was good enough\nas long as each crypto_alg came from exactly one module.\n\nHowever, with parameterised crypto algorithms a crypto_alg object may need\ntwo or more modules to operate.  This means that we need to count the\nreferences to the crypto_alg object directly.\n\nSigned-off-by: Herbert Xu \u003cherbert@gondor.apana.org.au\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n"
    },
    {
      "commit": "5cb1454b862ab3040b78364d58330262fea1ddba",
      "tree": "7e62126fa1f1398bb6a6b7f9e136aece32b0e112",
      "parents": [
        "06ace7a9bafeb9047352707eb79e8eaa0dfdf5f2"
      ],
      "author": {
        "name": "Herbert Xu",
        "email": "herbert@gondor.apana.org.au",
        "time": "Sat Nov 05 16:58:14 2005 +1100"
      },
      "committer": {
        "name": "David S. Miller",
        "email": "davem@sunset.davemloft.net",
        "time": "Mon Jan 09 14:15:37 2006 -0800"
      },
      "message": "[CRYPTO] Allow multiple implementations of the same algorithm\n\nThis is the first step on the road towards asynchronous support in\nthe Crypto API.  It adds support for having multiple crypto_alg objects\nfor the same algorithm registered in the system.\n\nFor example, each device driver would register a crypto_alg object\nfor each algorithm that it supports.  While at the same time the\nuser may load software implementations of those same algorithms.\n\nUsers of the Crypto API may then select a specific implementation\nby name, or choose any implementation for a given algorithm with\nthe highest priority.\n\nThe priority field is a 32-bit signed integer.  In future it will be\npossible to modify it from user-space.\n\nThis also provides a solution to the problem of selecting amongst\nvarious AES implementations, that is, aes vs. aes-i586 vs. aes-padlock.\n\nSigned-off-by: Herbert Xu \u003cherbert@gondor.apana.org.au\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"
    }
  ]
}