* Re: [for-next][PATCH 01/15] tracing: Switch trace.c code over to use guard()
[not found] <20241226143934.814245543@goodmis.org>
@ 2024-12-28 10:40 ` Markus Elfring
0 siblings, 0 replies; only message in thread
From: Markus Elfring @ 2024-12-28 10:40 UTC (permalink / raw)
To: Steven Rostedt, linux-trace-kernel
Cc: LKML, kernel-janitors, Andrew Morton, Mark Rutland,
Masami Hiramatsu, Mathieu Desnoyers, Peter Zijlstra
…
> 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
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2024-12-28 10:41 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <20241226143934.814245543@goodmis.org>
2024-12-28 10:40 ` [for-next][PATCH 01/15] tracing: Switch trace.c code over to use guard() Markus Elfring
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).