)]}'
{
  "commit": "08a2c6019ce873a24377a8b98cad1bff7546ca48",
  "tree": "1e0a69a65f4ef9b6cefbb155314826745c23ec88",
  "parents": [
    "0998cdfba1785765bfbf8ca1836a299943d12722"
  ],
  "author": {
    "name": "Paul Sokolovsky",
    "email": "paul.sokolovsky@linaro.org",
    "time": "Sun Jun 04 14:28:04 2017 +0300"
  },
  "committer": {
    "name": "Jukka Rissanen",
    "email": "jukka.rissanen@linux.intel.com",
    "time": "Mon Jun 05 10:32:28 2017 +0300"
  },
  "message": "net: context: Operations on unused context should lead to EBADF.\n\nSemantics of ENOENT error as used previously is \"named entity not\nfound\", whereas for \"I/O handle is not valid\", there\u0027s EBADF. For\nexample, POSIX/SUSV2 doesn\u0027t even list ENOENT as a possible error\nfor accept(), connect(), recv(), etc. whereas it lists EBADF, e.g.:\nhttp://pubs.opengroup.org/onlinepubs/7908799/xns/connect.html\n\nSigned-off-by: Paul Sokolovsky \u003cpaul.sokolovsky@linaro.org\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "1da453727ce68727b7161cc52619faf829a4c30d",
      "old_mode": 33188,
      "old_path": "subsys/net/ip/net_context.c",
      "new_id": "fce03a6d6368e7b83d10fcf7e07aef7e72daacb7",
      "new_mode": 33188,
      "new_path": "subsys/net/ip/net_context.c"
    }
  ]
}