)]}'
{
  "commit": "acf7b28ec09b998c8c75ffbbfdeb565ee9156c08",
  "tree": "0701a643d36ab966697dcbc0a9d503bb573fca84",
  "parents": [
    "4e9e220985ec9541cc3fd598c57f0834d4836cc1"
  ],
  "author": {
    "name": "Kelvin Zhang",
    "email": "zhangkelvin@google.com",
    "time": "Sun Nov 01 20:50:05 2026 -0800"
  },
  "committer": {
    "name": "David Gibson",
    "email": "david@gibson.dropbear.id.au",
    "time": "Mon Nov 02 16:07:22 2026 +1100"
  },
  "message": "libfdt: Don\u0027t search for the terminator in fdt_get_string()\n\nUnless FDT_ASSUME_MASK includes ASSUME_VALID_INPUT, fdt_get_string()\nfinds the end of the string with memchr(), bounded by the end of the\nstring block, which also checks that the string is terminated. A\nstring block normally ends with a NUL, and then every string in it is\nterminated. When the caller does not ask for the string\u0027s length,\ncheck that byte instead, so that fdt_string() doesn\u0027t scan the string\nat all.\n\nThis helps callers that look up many property names. With a 612 KiB\ntree on x86-64, built with gcc -O2 and the default FDT_ASSUME_MASK,\ncalling fdt_string() for the name of each of its 17,899 properties\ntakes 108 us instead of 160 us, not counting the walk that finds\nthem. libufdt, which Android bootloaders use to apply overlays, calls\nfdt_string() at least once for every property it reads: tens of\nthousands of times to apply one overlay to a 445 KiB tree.\n\nReviewed-by: David Gibson \u003cdavid@gibson.dropbear.id.au\u003e\nSigned-off-by: Kelvin Zhang \u003czhangkelvin@google.com\u003e\nMessage-ID: \u003cCAOSmRzixCf479QyhmGuwBBZrRLTYqoaSUw88HKZnkPyEh6\u003dgcw@mail.gmail.com\u003e\nSigned-off-by: David Gibson \u003cdavid@gibson.dropbear.id.au\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "ddfb8b93d4c5fccc973f875b6bdecd5b2a7e55b4",
      "old_mode": 33188,
      "old_path": "libfdt/fdt_ro.c",
      "new_id": "fed2f9fbd7a81868cf8fed330ee8e0b5643c1f0b",
      "new_mode": 33188,
      "new_path": "libfdt/fdt_ro.c"
    }
  ]
}
