)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":1000021,"name":"Antonio Borneo","email":"borneo.antonio@gmail.com","username":"borneoa"},"change_message_id":"8eb9c72727b0a418b9beecf4d04dd833627ae500","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"3e2bdc9b_5d1ba1e7","updated":"2024-09-14 17:16:09.000000000","message":"same comment as in previous patch in this series.\nHow to handle the merge in riscv fork?","commit_id":"ac0051996148b21bfc0d2029a783871e397cf77e"},{"author":{"_account_id":1002047,"name":"Evgeniy Naydanov","email":"eugnay@gmail.com","username":"en-sc"},"change_message_id":"15808363f3b7deb2f61bed570a621c927bba3e08","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"6a7d7d6a_206a1b69","in_reply_to":"3e2bdc9b_5d1ba1e7","updated":"2024-09-16 17:24:25.000000000","message":"Applying this patch creates 9 merge conflicts. Most are related to the change to `batch.h/c`.\nHowever, I don\u0027t see anything that would prevent that patch from being merged into RISC-V fork.","commit_id":"ac0051996148b21bfc0d2029a783871e397cf77e"}]}