Re: [for-next][PATCH 01/15] tracing: Switch trace.c code over to use guard()

[Markus Elfring]

…
> Switch every location that ends with unlocking a mutex or freeing on error
> over to using the guard(mutex)() and __free() infrastructure

Do any contributors find it safer and cleaner to separate adjustments for
these programming interfaces?
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.13-rc4#n81


>                                                              to let the
> compiler worry about releasing locks. …

May the compiler take care of further code transformation concerns?

Regards,
Markus