)]}'
{
  "log": [
    {
      "commit": "15f8c604a79c4840ed76eecf3af5d88b7c1dee9e",
      "tree": "d86815bc2daf835fee081ee7dac92cef8784f6a3",
      "parents": [
        "3c5df5c26ed17828760945d59653a2e22e3fb63f"
      ],
      "author": {
        "name": "Scott Wood",
        "email": "scottwood@freescale.com",
        "time": "Fri Sep 28 14:06:16 2007 -0500"
      },
      "committer": {
        "name": "Kumar Gala",
        "email": "galak@kernel.crashing.org",
        "time": "Thu Oct 04 15:47:05 2007 -0500"
      },
      "message": "[POWERPC] cpm: Describe multi-user ram in its own device node.\n\nThe way the current CPM binding describes available multi-user (a.k.a.\ndual-ported) RAM doesn\u0027t work well when there are multiple free regions,\nand it doesn\u0027t work at all if the region doesn\u0027t begin at the start of\nthe muram area (as the hardware needs to be programmed with offsets into\nthis area).  The latter situation can happen with SMC UARTs on CPM2, as its\nparameter RAM is relocatable, u-boot puts it at zero, and the kernel doesn\u0027t\nsupport moving it.\n\nIt is now described with a muram node, similar to QE.  The current CPM\nbinding is sufficiently recent (i.e. never appeared in an official release)\nthat compatibility with existing device trees is not an issue.\n\nThe code supporting the new binding is shared between cpm1 and cpm2, rather\nthan remain separated.  QE should be able to use this code as well, once\nminor fixes are made to its device trees.\n\nSigned-off-by: Scott Wood \u003cscottwood@freescale.com\u003e\nSigned-off-by: Kumar Gala \u003cgalak@kernel.crashing.org\u003e\n"
    }
  ]
}