)]}'
{
  "commit": "4fc96ee9085d39ceeaa7b60cd475d0a474e7062f",
  "tree": "5cb8ea9f9402411c704b15f16547a803f46e1058",
  "parents": [
    "319deec7db6c0aab276d2447f778e7cffed24c7c"
  ],
  "author": {
    "name": "Tycho Andersen",
    "email": "tycho@tycho.ws",
    "time": "Thu Dec 13 13:10:30 2018 -0700"
  },
  "committer": {
    "name": "Kees Cook",
    "email": "keescook@chromium.org",
    "time": "Thu Dec 13 16:51:01 2018 -0800"
  },
  "message": "seccomp, s390: fix build for syscall type change\n\nA recent patch landed in the security tree [1] that changed the type of the\nseccomp syscall. Unfortunately, I didn\u0027t quite get every instance of the\nforward declarations, and thus there is a build failure. Here\u0027s the last\none that I could find, for s390. It should go through the security tree,\nalthough hopefully some s390 people can check and make sure it looks\nreasonable?\n\nThe only oddity is the trailing semicolon; some lines around this patch\nhave it, and some lines don\u0027t. I\u0027ve left this one as-is.\n\n[1]: https://lore.kernel.org/lkml/20181212231630.GA31584@beast/T/#u\n\nSigned-off-by: Tycho Andersen \u003ctycho@tycho.ws\u003e\nFixes: 6a21cc50f0c7 (\"seccomp: add a return code to trap to userspace\")\nSigned-off-by: Kees Cook \u003ckeescook@chromium.org\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "2ce28bf0c5ec44939d815c5187153b0858475aa7",
      "old_mode": 33188,
      "old_path": "arch/s390/kernel/compat_wrapper.c",
      "new_id": "48c4ce668244ae57fc9cb0f5695ba276533be082",
      "new_mode": 33188,
      "new_path": "arch/s390/kernel/compat_wrapper.c"
    }
  ]
}