)]}'
{
  "commit": "d0bfd7c9b162612de55ca2d204403b90dc278db6",
  "tree": "f3bb0e4ca2aadceab29f0578857683d1ef02633b",
  "parents": [
    "a8ddd1b998bdad9489876a3068cc45917bee5441"
  ],
  "author": {
    "name": "Stephen Boyd",
    "email": "sboyd@codeaurora.org",
    "time": "Thu Oct 08 13:34:09 2015 -0500"
  },
  "committer": {
    "name": "Andy Gross",
    "email": "agross@codeaurora.org",
    "time": "Wed Oct 14 14:51:40 2015 -0500"
  },
  "message": "soc: qcom: smem: Move RPM message ram out of smem DT node\n\nSMEM is a software construct built on top of a DDR reserved region\nand sometimes a device memory region called RPM message ram. Having\nthe RPM message ram in the smem DT node\u0027s reg property leads to the\nsmem node being located in different places depending on if the\nmessage ram is being used or not. Let\u0027s add a qcom specific\nproperty, qcom,rpm-msg-ram, and point to the device memory from\nthe SMEM node via a phandle.  As SMEM is a software construct, it\nreally needs to reside at the root of the DT regardless of whether\nit\u0027s using the message ram or not.\n\nCc: Bjorn Andersson \u003cbjorn.andersson@sonymobile.com\u003e\nSigned-off-by: Stephen Boyd \u003csboyd@codeaurora.org\u003e\nSigned-off-by: Andy Gross \u003cagross@codeaurora.org\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "ab8e5725046809e53b9ef7ce39b1f6ca33d35dcc",
      "old_mode": 33188,
      "old_path": "arch/arm/boot/dts/qcom-msm8974.dtsi",
      "new_id": "93e315053bdd3c93e5c869b599a118f980f4f187",
      "new_mode": 33188,
      "new_path": "arch/arm/boot/dts/qcom-msm8974.dtsi"
    },
    {
      "type": "modify",
      "old_id": "74017114ce6e29c2341833176076bf27224ab8c5",
      "old_mode": 33188,
      "old_path": "drivers/soc/qcom/smem.c",
      "new_id": "19019aa092e86d76ad5a24b80f34616b9e38e320",
      "new_mode": 33188,
      "new_path": "drivers/soc/qcom/smem.c"
    }
  ]
}