)]}'
{
  "commit": "90aef12e6dd609e1ad7fb70044eedc78ca55ee5e",
  "tree": "35ff39f80d010c548df660d3a3e53c5861741777",
  "parents": [
    "74c383f1400f559562aa517d6d62f77245bddf52"
  ],
  "author": {
    "name": "Jeremy Fitzhardinge",
    "email": "jeremy@goop.org",
    "time": "Wed Dec 13 00:34:49 2006 -0800"
  },
  "committer": {
    "name": "Linus Torvalds",
    "email": "torvalds@woody.osdl.org",
    "time": "Wed Dec 13 09:05:51 2006 -0800"
  },
  "message": "[PATCH] Use activate_mm() in fs/aio.c:use_mm()\n\nactivate_mm() is not the right thing to be using in use_mm().  It should be\nswitch_mm().\n\nOn normal x86, they\u0027re synonymous, but for the Xen patches I\u0027m adding a\nhook which assumes that activate_mm is only used the first time a new mm\nis used after creation (I have another hook for dealing with dup_mm).  I\nthink this use of activate_mm() is the only place where it could be used\na second time on an mm.\n\n\u003eFrom a quick look at the other architectures I think this is OK (most\nsimply implement one in terms of the other), but some are doing some\nsubtly different stuff between the two.\n\nAcked-by: David Miller \u003cdavem@davemloft.net\u003e\nSigned-off-by: Andrew Morton \u003cakpm@osdl.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@osdl.org\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "d3a6ec2c9627e1e58a769c93398f2a3787bdfda8",
      "old_mode": 33188,
      "old_path": "fs/aio.c",
      "new_id": "5f577a63bdf0e18ed51a39047e599e073f1a48bf",
      "new_mode": 33188,
      "new_path": "fs/aio.c"
    }
  ]
}