)]}'
{
  "commit": "cdbc848b03414c75b7badccd8ada29deba7ec6e4",
  "tree": "651176bc2b4a59a7efa042bb6a6db8aad7b7123c",
  "parents": [
    "c756c592e442ba101c91daed3524ba5b3a784ba6"
  ],
  "author": {
    "name": "Florian Fainelli",
    "email": "f.fainelli@gmail.com",
    "time": "Mon Nov 05 14:54:30 2018 -0800"
  },
  "committer": {
    "name": "Rob Herring",
    "email": "robh@kernel.org",
    "time": "Mon Nov 26 15:50:39 2018 -0600"
  },
  "message": "of/fdt: Remove custom __early_init_dt_declare_initrd() implementation\n\nNow that ARM64 uses phys_initrd_start/phys_initrd_size, we can get rid\nof its custom __early_init_dt_declare_initrd() which causes a fair\namount of objects rebuild when changing CONFIG_BLK_DEV_INITRD. In order\nto make sure ARM64 does not produce a BUG() when VM debugging is turned\non though, we must avoid early calls to __va() which is what\n__early_init_dt_declare_initrd() does and wrap this around to avoid\nrunning that code on ARM64.\n\nSigned-off-by: Florian Fainelli \u003cf.fainelli@gmail.com\u003e\nReviewed-by: Mike Rapoport \u003crppt@linux.ibm.com\u003e\nSigned-off-by: Rob Herring \u003crobh@kernel.org\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "b96442960aead1692e94d28dd35d33e7954d84b3",
      "old_mode": 33188,
      "old_path": "arch/arm64/include/asm/memory.h",
      "new_id": "dc3ca21ba240b6bc930b19919f73af233e984ecb",
      "new_mode": 33188,
      "new_path": "arch/arm64/include/asm/memory.h"
    },
    {
      "type": "modify",
      "old_id": "88760a0983a72a31ed63e63e6feca15a7c0a62a3",
      "old_mode": 33188,
      "old_path": "drivers/of/fdt.c",
      "new_id": "cd72a41fcab229cc76ac26889a560590e41b776c",
      "new_mode": 33188,
      "new_path": "drivers/of/fdt.c"
    }
  ]
}