)]}'
{
  "commit": "844c0972427ee5f661158160aaca10b22b3dda60",
  "tree": "b4e7694efc8dbfbc88ecfcca97a2381f0144c046",
  "parents": [
    "4178ba462a3e8ab5094e69606f01d9e95f2d5ea6"
  ],
  "author": {
    "name": "Gustavo F. Padovan",
    "email": "padovan@profusion.mobi",
    "time": "Tue May 04 23:16:01 2010 -0300"
  },
  "committer": {
    "name": "Marcel Holtmann",
    "email": "marcel@holtmann.org",
    "time": "Mon May 10 09:28:53 2010 +0200"
  },
  "message": "Bluetooth: Fix spec error in the RemoteBusy Logic\n\nOn the receipt of an RR(P\u003d1) under RemoteBusy set to TRUE(on the RECV\nstate table) we have to call sendIorRRorRNR(F\u003d1) and just after set\nRemoteBusy to False. This leads to a freeze in the sending process since\nit\u0027s not allowed send data with RemoteBusy set to true and no one\ncall SendPending-I-Frames after set RemoteBusy to false(The last action\nfor that event).\n\nActually sendIorRRorRNR() calls SendPending-I-Frames but at that moment\nRemoteBusy is still True and we cannot send any frame, after, no one\ncalls SendPending-I-Frames again and the sending process stops.\n\nThe solution here is to set RemoteBusy to false inside\nSendPending-I-Frames just before call SendPending-I-Frames. That will\nmake SendPending-I-Frames able to send frames. This solution is similar\nto what RR(P\u003d0)(F\u003d0) on the RECV table and RR(P\u003d1) on the SREJ_SENT\ntable do.\n\nActually doesn\u0027t make any sense call SendPending-I-Frames if we can send\nany frame, i. e., RemoteBusy is True.\n\nSigned-off-by: Gustavo F. Padovan \u003cpadovan@profusion.mobi\u003e\nSigned-off-by: Marcel Holtmann \u003cmarcel@holtmann.org\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "9ef01c32b3a224cefd9e40fdd3c99403c937b878",
      "old_mode": 33188,
      "old_path": "net/bluetooth/l2cap.c",
      "new_id": "ba49f9a3579e119f413d49dff50df799b1fd56a9",
      "new_mode": 33188,
      "new_path": "net/bluetooth/l2cap.c"
    }
  ]
}