)]}'
{
  "commit": "25cdda10e1efad2eb3afbc70e55e6c9eafb3a8a4",
  "tree": "bed21a169595c10fb184ae4fe152ad4dd46a012e",
  "parents": [
    "8799ab1ec2fa9b61f3f0d9e40fcc3c3c3ee059d8"
  ],
  "author": {
    "name": "Lars-Ove Karlsson",
    "email": "lars-ove.karlsson@iar.com",
    "time": "Wed Jun 12 12:51:21 2024 +0200"
  },
  "committer": {
    "name": "Alberto Escolar",
    "email": "alberto.escolar.piedras@nordicsemi.no",
    "time": "Fri Jun 14 19:26:27 2024 +0200"
  },
  "message": "kernel: Unified type of stack protection canary __stack_chk_guard.\n\nExtern declaration of __stack_chk_guard added volatile to\nthe type while the declaration was non-volatile. This cause\ntype check errors with compilers that declares the\n__stack_chk_guard variable in an internal pre-include\nheader file (IAR).\n\nWhile I think the volatile keyword is unnecessary, I decided\non keep it and add it to the declaration in\nkernel/compiler_stack_protect.c\n\nTested with IAR ICCARM and the Zephyr SDK GCC.\n\nSigned-off-by: Lars-Ove Karlsson \u003clars-ove.karlsson@iar.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "2ee2d81c7a32017e7960b310b94f8b5443b9a9ce",
      "old_mode": 33188,
      "old_path": "kernel/compiler_stack_protect.c",
      "new_id": "928fdc6ec9ad8230c2ede9a8b03aa86253ea4a4c",
      "new_mode": 33188,
      "new_path": "kernel/compiler_stack_protect.c"
    }
  ]
}
