)]}'
{
  "log": [
    {
      "commit": "6cf1c5fc26c6507bcb0edced6fcda876a79b5a6d",
      "tree": "1c8fb5732344addc6336e8ba8c7c4154a6dac9ac",
      "parents": [
        "5b8ca5344f82e594e21c9fbbdf3b13507ecdb5a2"
      ],
      "author": {
        "name": "Andy King",
        "email": "acking@vmware.com",
        "time": "Mon Feb 18 06:04:13 2013 +0000"
      },
      "committer": {
        "name": "David S. Miller",
        "email": "davem@davemloft.net",
        "time": "Mon Feb 18 15:02:51 2013 -0500"
      },
      "message": "VSOCK: Don\u0027t reject PF_VSOCK protocol\n\nAllow our own family as the protocol value for socket creation.\n\nReported-by: Gerd Hoffmann \u003ckraxel@redhat.com\u003e\nSigned-off-by: Andy King \u003cacking@vmware.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n"
    },
    {
      "commit": "7ccd7de691bcc7194deb68b1db391861ada5427e",
      "tree": "061bc8ce013d54ec5ae5b4dcf03702c69cc46ee7",
      "parents": [
        "7777ac3860327da557665f6e53cd82fbe40f151b"
      ],
      "author": {
        "name": "Dmitry Torokhov",
        "email": "dtor@vmware.com",
        "time": "Mon Feb 18 06:04:11 2013 +0000"
      },
      "committer": {
        "name": "David S. Miller",
        "email": "davem@davemloft.net",
        "time": "Mon Feb 18 15:02:51 2013 -0500"
      },
      "message": "VSOCK: get rid of vsock_version.h\n\nThere isn\u0027t really a need to have a separate file for it.\n\nAcked-by: Andy King \u003cacking@vmware.com\u003e\nSigned-off-by: Dmitry Torokhov \u003cdtor@vmware.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n"
    },
    {
      "commit": "7777ac3860327da557665f6e53cd82fbe40f151b",
      "tree": "e7a7a1d53c17524f37442e600ae6f7d8e4cbf58e",
      "parents": [
        "c2399059a389ba686fa7f45d8913a708914752c4"
      ],
      "author": {
        "name": "Dmitry Torokhov",
        "email": "dtor@vmware.com",
        "time": "Mon Feb 18 06:04:10 2013 +0000"
      },
      "committer": {
        "name": "David S. Miller",
        "email": "davem@davemloft.net",
        "time": "Mon Feb 18 15:02:51 2013 -0500"
      },
      "message": "VSOCK: get rid of EXPORT_SYMTAB\n\nThis is the default behavior for a looooooong time.\n\nAcked-by: Andy King \u003cacking@vmware.com\u003e\nSigned-off-by: Dmitry Torokhov \u003cdtor@vmware.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n"
    },
    {
      "commit": "d021c344051af91f42c5ba9fdedc176740cbd238",
      "tree": "8c02cd94a59556da4b74823816e670dd007db72f",
      "parents": [
        "fd5023111cf720db890ef34f305ac5d427e690a0"
      ],
      "author": {
        "name": "Andy King",
        "email": "acking@vmware.com",
        "time": "Wed Feb 06 14:23:56 2013 +0000"
      },
      "committer": {
        "name": "David S. Miller",
        "email": "davem@davemloft.net",
        "time": "Sun Feb 10 19:41:08 2013 -0500"
      },
      "message": "VSOCK: Introduce VM Sockets\n\nVM Sockets allows communication between virtual machines and the hypervisor.\nUser level applications both in a virtual machine and on the host can use the\nVM Sockets API, which facilitates fast and efficient communication between\nguest virtual machines and their host.  A socket address family, designed to be\ncompatible with UDP and TCP at the interface level, is provided.\n\nToday, VM Sockets is used by various VMware Tools components inside the guest\nfor zero-config, network-less access to VMware host services.  In addition to\nthis, VMware\u0027s users are using VM Sockets for various applications, where\nnetwork access of the virtual machine is restricted or non-existent.  Examples\nof this are VMs communicating with device proxies for proprietary hardware\nrunning as host applications and automated testing of applications running\nwithin virtual machines.\n\nThe VMware VM Sockets are similar to other socket types, like Berkeley UNIX\nsocket interface.  The VM Sockets module supports both connection-oriented\nstream sockets like TCP, and connectionless datagram sockets like UDP. The VM\nSockets protocol family is defined as \"AF_VSOCK\" and the socket operations\nsplit for SOCK_DGRAM and SOCK_STREAM.\n\nFor additional information about the use of VM Sockets, please refer to the\nVM Sockets Programming Guide available at:\n\nhttps://www.vmware.com/support/developer/vmci-sdk/\n\nSigned-off-by: George Zhang \u003cgeorgezhang@vmware.com\u003e\nSigned-off-by: Dmitry Torokhov \u003cdtor@vmware.com\u003e\nSigned-off-by: Andy king \u003cacking@vmware.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n"
    }
  ]
}