)]}'
{
  "commit": "a9a4e39fd2bbf09bf10cb30700f4792a10cd2392",
  "tree": "5e6b41b6a463e6558232ce88ec302a9e39de7fb3",
  "parents": [
    "96b1b00058fc95de6c76c441a8b941003de3a54d"
  ],
  "author": {
    "name": "Daniel Henrique Barboza",
    "email": "dbarboza@ventanamicro.com",
    "time": "Fri Feb 24 14:45:19 2023 -0300"
  },
  "committer": {
    "name": "Palmer Dabbelt",
    "email": "palmer@rivosinc.com",
    "time": "Wed Mar 01 17:40:14 2023 -0800"
  },
  "message": "target/riscv/csr.c: use riscv_cpu_cfg() to avoid env_cpu() pointers\n\nA common trend in this file is to retrieve a RISCVCPU pointer by first\nretrieving a CPUState pointer via env_cpu(). The CPU pointer is used\nonly to access the RISCVCPUConfig object and nothing else.\n\nLet\u0027s use riscv_cpu_cfg() to access what we need directly without these\n2 pointers.\n\nSuggested-by: LIU Zhiwei \u003czhiwei_liu@linux.alibaba.com\u003e\nSigned-off-by: Daniel Henrique Barboza \u003cdbarboza@ventanamicro.com\u003e\nReviewed-by: Weiwei Li \u003cliweiwei@iscas.ac.cn\u003e\nReviewed-by: Richard Henderson \u003crichard.henderson@linaro.org\u003e\nMessage-ID: \u003c20230224174520.92490-4-dbarboza@ventanamicro.com\u003e\nSigned-off-by: Palmer Dabbelt \u003cpalmer@rivosinc.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "bf456fe87c0ad658f55160191b64c7d59dee2ba9",
      "old_mode": 33188,
      "old_path": "target/riscv/csr.c",
      "new_id": "86e183feb3eb112a44a67ea7cdf08bae90830220",
      "new_mode": 33188,
      "new_path": "target/riscv/csr.c"
    }
  ]
}