Re: [PATCH v2] locking/local_lock: s/l/l/ and s/tl/tl/ to reduce risk of shadowing

Next message: Christian Brauner: "Re: [syzbot] [fs?] BUG: sleeping function called from invalid context in hook_sb_delete"
Previous message: Andrew Murray: "Re: [RFC 0/1] serial: 8250: nbcon_atomic_flush_pending() might trigger watchdog warnigns"
In reply to: Vlastimil Babka: "Re: [PATCH v2] locking/local_lock: s/l/__l/ and s/tl/__tl/ to reduce risk of shadowing"
Next in thread: Sebastian Andrzej Siewior: "Re: [PATCH v2] locking/local_lock: s/l/__l/ and s/tl/__tl/ to reduce risk of shadowing"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

From: Vincent Mailhol

Date: Mon Sep 29 2025 - 04:51:00 EST

On 9/26/25 11:16 PM, Vlastimil Babka wrote:
> +CC LOCKING PRIMITIVES maintainers. Looks like local_lock files were never
> added to the section, should we?

Shall I resend with the correct list of persons in CC? Or is it OK as-is?

Yours sincerely,
Vincent Mailhol

Re: [PATCH v2] locking/local_lock: s/l/__l/ and s/tl/__tl/ to reduce risk of shadowing

Re: [PATCH v2] locking/local_lock: s/l/l/ and s/tl/tl/ to reduce risk of shadowing