)]}'
{
  "log": [
    {
      "commit": "68648ed1f58d98b8e8d994022e5e25331fbfe42a",
      "tree": "77c721d08b11aba58a30779e7b3294a96dd7fb29",
      "parents": [
        "a42dc9d4804cc5e111952008492dae9d34c6a541"
      ],
      "author": {
        "name": "Antonino A. Daplas",
        "email": "adaplas@gmail.com",
        "time": "Tue May 08 00:38:57 2007 -0700"
      },
      "committer": {
        "name": "Linus Torvalds",
        "email": "torvalds@woody.linux-foundation.org",
        "time": "Tue May 08 11:15:30 2007 -0700"
      },
      "message": "fbdev: add drawing functions for framebuffers in system RAM\n\nThe generic drawing functions (cfbimgblt, cfbcopyarea, cfbfillrect) assume\nthat the framebuffer is in IO memory.  However, we have 3 drivers (hecubafb,\narcfb, and vfb) where the framebuffer is allocated from system RAM (via\nvmalloc). Using _raw_read/write and family for these drivers (as used in\nthe cfb* functions) is illegal, especially in other platforms.\n\nCreate 3 new drawing functions, based almost entirely from the original\nexcept that the framebuffer memory is assumed to be in system RAM.\nThese are named as sysimgblt, syscopyarea, and sysfillrect.\n\nSigned-off-by: Antonino Daplas \u003cadaplas@gmail.com\u003e\nSigned-off-by: Andrew Morton \u003cakpm@linux-foundation.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\n"
    }
  ]
}