)]}'
{
  "commit": "86eb76f0104edbffa99aec7905ffba49274868c0",
  "tree": "dcf098f94d98b25430d5f9f68dba0ad9912ff3a5",
  "parents": [
    "cd1d41e869022be23d345d47b679d1924c1db794",
    "c340e8a2ba6ec43522044af10fc03258d9abc462"
  ],
  "author": {
    "name": "Jonathan Brouwer",
    "email": "jonathantbrouwer@gmail.com",
    "time": "Tue Jun 30 04:06:56 2026 +0200"
  },
  "committer": {
    "name": "GitHub",
    "email": "noreply@github.com",
    "time": "Tue Jun 30 04:06:56 2026 +0200"
  },
  "message": "Rollup merge of #157445 - pmur:murp/extend-patchable, r\u003dmejrs\n\nAllow section override when using patchable-function-entries\n\nSometimes it is necessary to group patchable function entrypoint records in distinct linker sections. This is the case for some bpf functions within the linux kernel which shouldn\u0027t be visible to ftrace.\n\nExtend `-Zpatchable-function-entry` to accept an argument of the form `prefix_nops,total_nops,record_section`, which places all entry record into a user specified section.\n\nLikewise, extend the `patchable_function_entry` attribute to accept an optional `section\u003d\"name\"` option to place a function into a specific section.\n\nThis is made possible by llvm attribute `patchable-function-entry-section` added in llvm 21.\n",
  "tree_diff": []
}