)]}'
{
  "commit": "fa1b47dd85453ec7d4bcfe4aa4a2d172ba452fc3",
  "tree": "3e5f14cccd9e4ec772310c1b2792b6f4b84bf7cb",
  "parents": [
    "e45f2e2bd298e1ff687448e5fd15a3588b5807ec"
  ],
  "author": {
    "name": "Steven Rostedt",
    "email": "srostedt@redhat.com",
    "time": "Thu Apr 02 00:09:41 2009 -0400"
  },
  "committer": {
    "name": "Ingo Molnar",
    "email": "mingo@elte.hu",
    "time": "Tue Apr 14 00:00:53 2009 +0200"
  },
  "message": "ring-buffer: add ring_buffer_discard_commit\n\nThe ring_buffer_discard_commit is similar to ring_buffer_event_discard\nbut it can only be done on an event that has yet to be commited.\nUnpredictable results can happen otherwise.\n\nThe main difference between ring_buffer_discard_commit and\nring_buffer_event_discard is that ring_buffer_discard_commit will try\nto free the data in the ring buffer if nothing has addded data\nafter the reserved event. If something did, then it acts almost the\nsame as ring_buffer_event_discard followed by a\nring_buffer_unlock_commit.\n\nNote, either ring_buffer_commit_discard and ring_buffer_unlock_commit\ncan be called on an event, not both.\n\nThis commit also exports both discard functions to be usable by\nGPL modules.\n\nSigned-off-by: Steven Rostedt \u003csrostedt@redhat.com\u003e\nSigned-off-by: Ingo Molnar \u003cmingo@elte.hu\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "e1b7b2173885f8f14f4a8da3979d0a6eff08e186",
      "old_mode": 33188,
      "old_path": "include/linux/ring_buffer.h",
      "new_id": "f0aa486d131c6f41120a8a39731f5df31deb2eee",
      "new_mode": 33188,
      "new_path": "include/linux/ring_buffer.h"
    },
    {
      "type": "modify",
      "old_id": "74a11808c282e2cf6b8b4cd9ddb6aaa8bcec87af",
      "old_mode": 33188,
      "old_path": "kernel/trace/ring_buffer.c",
      "new_id": "f935bd5ec3e839e9735e4efbc4072fa93348ac88",
      "new_mode": 33188,
      "new_path": "kernel/trace/ring_buffer.c"
    }
  ]
}