Hi Chahuan,
Sorry for the late reply. Honestly I haven't found time to test a
arm64 vmcore against your patch, that's why I didn't update the
status. In addition, there is some urgent issue that lianbo and I are
currently dealing with internally, so a delayed upstream work is more
likely to happen. Your patches are in our work queue. Again, I'm very
sorry for any inconvenience.
Thanks,
Tao Liu
On Tue, Apr 14, 2026 at 8:21 PM chahuan <chahuan(a)qti.qualcomm.com> wrote:
Hi Tao,
Friendly ping — it's been about two weeks since I sent the last reply,
so I wanted to check in and see if there are any remaining concerns or
anything I missed.
If there are any design concerns — e.g. about the scope-guard approach,
the gdb patch boundary, the helper APIs
(`set_temporary_datatype_filename` / `restore_datatype_filename`), or
the failure semantics for ambiguous file matches — I am happy to revise.
A v2 with whatever changes are needed is no problem at all.
Also, I subscribed to the mailing list (devel(a)lists.crash-utility.osci.io)
but my subscription request has been pending and not yet approved. If
someone could help approve it, that would be much appreciated.
Please let me know if there is anything blocking acceptance, or if the
patch simply needs more time on the review queue. Either way, feedback
is very welcome.
Thank you for your time.
Best regards,
chahuan