)]}'
{
  "log": [
    {
      "commit": "0ad6614048cf722e4d27909665b4846805357f1b",
      "tree": "182349ddf6e2b8e8478a5451cd0ed9684c14f0e8",
      "parents": [
        "d9e31d17ceba5f0736f5a34bbc236239cd42b420"
      ],
      "author": {
        "name": "James Chapman",
        "email": "jchapman@katalix.com",
        "time": "Fri Apr 02 06:19:33 2010 +0000"
      },
      "committer": {
        "name": "David S. Miller",
        "email": "davem@davemloft.net",
        "time": "Sat Apr 03 14:56:07 2010 -0700"
      },
      "message": "l2tp: Add debugfs files for dumping l2tp debug info\n\nThe existing pppol2tp driver exports debug info to\n/proc/net/pppol2tp. Rather than adding info to that file for the new\nfunctionality added in this patch series, we add new files in debugfs,\nleaving the old /proc file for backwards compatibility (L2TPv2 only).\n\nCurrently only one file is provided: l2tp/tunnels, which lists\ninternal debug info for all l2tp tunnels and sessions. More files may\nbe added later. The info is for debug and problem analysis only -\nuserspace apps should use netlink to obtain status about l2tp tunnels\nand sessions.\n\nAlthough debugfs does not support net namespaces, the tunnels and\nsessions dumped in l2tp/tunnels are only those in the net namespace of\nthe process reading the file.\n\nSigned-off-by: James Chapman \u003cjchapman@katalix.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n"
    },
    {
      "commit": "d9e31d17ceba5f0736f5a34bbc236239cd42b420",
      "tree": "d31a8fb8365c85db07b649a5d5aa11069890de23",
      "parents": [
        "e02d494d2c60746ee6583132904ac1791f5bc9a6"
      ],
      "author": {
        "name": "James Chapman",
        "email": "jchapman@katalix.com",
        "time": "Fri Apr 02 06:19:26 2010 +0000"
      },
      "committer": {
        "name": "David S. Miller",
        "email": "davem@davemloft.net",
        "time": "Sat Apr 03 14:56:06 2010 -0700"
      },
      "message": "l2tp: Add L2TP ethernet pseudowire support\n\nThis driver presents a regular net_device for each L2TP ethernet\npseudowire instance. These interfaces are named l2tpethN by default,\nthough userspace can specify an alternative name when the L2TP\nsession is created, if preferred. When the pseudowire is established,\nregular Linux networking utilities may be used to configure the\ninterface, i.e. give it IP address info or add it to a bridge. Any\ndata passed over the interface is carried over an L2TP tunnel.\n\nSigned-off-by: James Chapman \u003cjchapman@katalix.com\u003e\nReviewed-by: Randy Dunlap \u003crandy.dunlap@oracle.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n"
    },
    {
      "commit": "309795f4bec2d69cd507a631f82065c2198a0825",
      "tree": "b3676be9a8f65f0d828a07e3bd6906bf7cd7b664",
      "parents": [
        "f408e0ce40270559ef80f231843c93baa9947bc5"
      ],
      "author": {
        "name": "James Chapman",
        "email": "jchapman@katalix.com",
        "time": "Fri Apr 02 06:19:10 2010 +0000"
      },
      "committer": {
        "name": "David S. Miller",
        "email": "davem@davemloft.net",
        "time": "Sat Apr 03 14:56:05 2010 -0700"
      },
      "message": "l2tp: Add netlink control API for L2TP\n\nIn L2TPv3, we need to create/delete/modify/query L2TP tunnel and\nsession contexts. The number of parameters is significant. So let\u0027s\nuse netlink. Userspace uses this API to control L2TP tunnel/session\ncontexts in the kernel.\n\nThe previous pppol2tp driver was managed using [gs]etsockopt(). This\nAPI is retained for backwards compatibility. Unlike L2TPv2 which\ncarries only PPP frames, L2TPv3 can carry raw ethernet frames or other\nframe types and these do not always have an associated socket\nfamily. Therefore, we need a way to use L2TP sessions that doesn\u0027t\nrequire a socket type for each supported frame type. Hence netlink is\nused.\n\nSigned-off-by: James Chapman \u003cjchapman@katalix.com\u003e\nReviewed-by: Randy Dunlap \u003crandy.dunlap@oracle.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n"
    },
    {
      "commit": "0d76751fad7739014485ba5bd388d4f1b4fd4143",
      "tree": "25a4525bf6b2ec9f052f22ba98cdfd3ff3a86aa3",
      "parents": [
        "e0d4435f93905f517003cfa7328a36ea19788147"
      ],
      "author": {
        "name": "James Chapman",
        "email": "jchapman@katalix.com",
        "time": "Fri Apr 02 06:19:00 2010 +0000"
      },
      "committer": {
        "name": "David S. Miller",
        "email": "davem@davemloft.net",
        "time": "Sat Apr 03 14:56:04 2010 -0700"
      },
      "message": "l2tp: Add L2TPv3 IP encapsulation (no UDP) support\n\nThis patch adds a new L2TPIP socket family and modifies the core to\nhandle the case where there is no UDP header in the L2TP\npacket. L2TP/IP uses IP protocol 115. Since L2TP/UDP and L2TP/IP\npackets differ in layout, the datapath packet handling code needs\nchanges too. Userspace uses an L2TPIP socket instead of a UDP socket\nwhen IP encapsulation is required.\n\nWe can\u0027t use raw sockets for this because the semantics of raw sockets\ndon\u0027t lend themselves to the socket-per-tunnel model - we need to\n\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n"
    },
    {
      "commit": "fd558d186df2c13a22455373858bae634a4795af",
      "tree": "ed05523913473b6ba7658c6e8d72a1642cce1851",
      "parents": [
        "21b4aaa14329db793832e865f15000c5c0192ac3"
      ],
      "author": {
        "name": "James Chapman",
        "email": "jchapman@katalix.com",
        "time": "Fri Apr 02 06:18:33 2010 +0000"
      },
      "committer": {
        "name": "David S. Miller",
        "email": "davem@davemloft.net",
        "time": "Sat Apr 03 14:56:02 2010 -0700"
      },
      "message": "l2tp: Split pppol2tp patch into separate l2tp and ppp parts\n\nThis patch splits the pppol2tp driver into separate L2TP and PPP parts\nto prepare for L2TPv3 support. In L2TPv3, protocols other than PPP can\nbe carried, so this split creates a common L2TP core that will handle\nthe common L2TP bits which protocol support modules such as PPP will\nuse.\n\nNote that the existing pppol2tp module is split into l2tp_core and\nl2tp_ppp by this change.\n\nThere are no feature changes here. Internally, however, there are\nsignificant changes, mostly to handle the separation of PPP-specific\ndata from the L2TP session and to provide hooks in the core for\nmodules like PPP to access.\n\nSigned-off-by: James Chapman \u003cjchapman@katalix.com\u003e\nReviewed-by: Randy Dunlap \u003crandy.dunlap@oracle.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n"
    },
    {
      "commit": "21b4aaa14329db793832e865f15000c5c0192ac3",
      "tree": "0cafa9589701dec0c39da0fbef5d7c7df0c987dc",
      "parents": [
        "22bedad3ce112d5ca1eaf043d4990fa2ed698c87"
      ],
      "author": {
        "name": "James Chapman",
        "email": "jchapman@katalix.com",
        "time": "Fri Apr 02 06:18:28 2010 +0000"
      },
      "committer": {
        "name": "David S. Miller",
        "email": "davem@davemloft.net",
        "time": "Sat Apr 03 14:56:01 2010 -0700"
      },
      "message": "l2tp: Relocate pppol2tp driver to new net/l2tp directory\n\nThis patch moves the existing pppol2tp driver from drivers/net into a\nnew net/l2tp directory, which is where the upcoming L2TPv3 code will\nlive. The existing CONFIG_PPPOL2TP config option is left in its\ncurrent place to avoid \"make oldconfig\" issues when an existing\npppol2tp user takes this change. (This is the same approach used for\nthe pppoatm driver, which moved to net/atm.)\n\nThere are no code changes. The existing drivers/net/pppol2tp.c is\nsimply moved to net/l2tp.\n\nSigned-off-by: James Chapman \u003cjchapman@katalix.com\u003e\nReviewed-by: Randy Dunlap \u003crandy.dunlap@oracle.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n"
    }
  ]
}