)]}'
{
  "commit": "1bf145fed572583d4cb7c1784689a0b42c997ba6",
  "tree": "3ef524b2af2ea77f2ea99478b8a4058a8cf07d13",
  "parents": [
    "a481e97d3cdc40b9d58271675bd4f0abb79d4872"
  ],
  "author": {
    "name": "Stefan Richter",
    "email": "stefanr@s5r6.in-berlin.de",
    "time": "Mon Aug 16 23:45:54 2010 +0200"
  },
  "committer": {
    "name": "Stefan Richter",
    "email": "stefanr@s5r6.in-berlin.de",
    "time": "Thu Aug 19 20:28:25 2010 +0200"
  },
  "message": "firewire: net: fix unicast reception RCODE in failure paths\n\nThe incoming request hander fwnet_receive_packet() expects subsequent\ndatagram handling code to return non-zero on errors.  However, almost\nnone of the failure paths did so.  Fix them all.\n\n(This error reporting is used to send and RCODE_CONFLICT_ERROR to the\nsender node in such failure cases.  Two modes of failure exist:  Out of\nmemory, or firewire-net is unaware of any peer node to which a fragment\nor an ARP packet belongs.  However, it is unclear whether a sender can\nactually make use of such information.  A Linux peer apparently can\u0027t.\nMaybe it should all be simplified to void functions.)\n\nReported-by: Julia Lawall \u003cjulia@diku.dk\u003e\nSigned-off-by: Stefan Richter \u003cstefanr@s5r6.in-berlin.de\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "da17d409a244b0af97249341855dfe301b506ab3",
      "old_mode": 33188,
      "old_path": "drivers/firewire/net.c",
      "new_id": "33f8421c71cc05001c57bbf275b61679fded72eb",
      "new_mode": 33188,
      "new_path": "drivers/firewire/net.c"
    }
  ]
}