)]}'
{
  "commit": "3e65646bb12be03b14dff53907391095a52d5f49",
  "tree": "5ab2961f02a2d078990e69584af81b1197fb2392",
  "parents": [
    "3efb40c2c6eea315abcf19239c15d088e2498299"
  ],
  "author": {
    "name": "Inaky Perez-Gonzalez",
    "email": "inaky@linux.intel.com",
    "time": "Sat Dec 20 16:57:38 2008 -0800"
  },
  "committer": {
    "name": "Greg Kroah-Hartman",
    "email": "gregkh@suse.de",
    "time": "Wed Jan 07 10:00:17 2009 -0800"
  },
  "message": "wimax: basic API: kernel/user messaging, rfkill and reset\n\nImplements the three basic operations provided by the stack\u0027s control\ninterface to WiMAX devices:\n\n- Messaging channel between user space and driver/device\n\n  This implements a direct communication channel between user space\n  and the driver/device, by which free form messages can be sent back\n  and forth.\n\n  This is intended for device-specific features, vendor quirks, etc.\n\n- RF-kill framework integration\n\n  Provide most of the RF-Kill integration for WiMAX drivers so that\n  all device drivers have to do is after wimax_dev_add() is call\n  wimax_report_rfkill_{hw,sw}() to update initial state and then every\n  time it changes.\n\n  Provides wimax_rfkill() for the kernel to call to set software\n  RF-Kill status and/or query current hardware and software switch\n  status.\n\n  Exports wimax_rfkill() over generic netlink to user space.\n\n- Reset a WiMAX device\n\n  Provides wimax_reset() for the kernel to reset a wimax device as\n  needed and exports it over generic netlink to user space.\n\nThis API is clearly limited, as it still provides no way to do the\nbasic scan, connect and disconnect in a hardware independent way.  The\nWiMAX case is more complex than WiFi due to the way networks are\ndiscovered and provisioned.\n\nThe next developments are to add the basic operations so they can be\nofferent by different drivers. However, we\u0027d like to get more vendors\nto jump in and provide feedback of how the user/kernel API/abstraction\nlayer should be.\n\nThe user space code for the i2400m, as of now, uses the messaging\nchannel, but that will change as the API evolves.\n\nSigned-off-by: Inaky Perez-Gonzalez \u003cinaky@linux.intel.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@suse.de\u003e\n\n",
  "tree_diff": [
    {
      "type": "add",
      "old_id": "0000000000000000000000000000000000000000",
      "old_mode": 0,
      "old_path": "/dev/null",
      "new_id": "cb3b4ad53683682be59abe46d215d0417612ea1d",
      "new_mode": 33188,
      "new_path": "net/wimax/op-msg.c"
    },
    {
      "type": "add",
      "old_id": "0000000000000000000000000000000000000000",
      "old_mode": 0,
      "old_path": "/dev/null",
      "new_id": "ca269178c4d4efea02fab6a84f43934a1e0e9905",
      "new_mode": 33188,
      "new_path": "net/wimax/op-reset.c"
    },
    {
      "type": "add",
      "old_id": "0000000000000000000000000000000000000000",
      "old_mode": 0,
      "old_path": "/dev/null",
      "new_id": "8745bac173f182aa5bd7fe79161585fde4a12efa",
      "new_mode": 33188,
      "new_path": "net/wimax/op-rfkill.c"
    }
  ]
}