From: Jacques Nilo <jnilo@free.fr>
To: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jirislaby@kernel.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org,
Jacques Nilo <jnilo@free.fr>
Subject: Re: [PATCH 1/3] serial: core: introduce guard(uart_port_lock_sysrq_irqsave)
Date: Wed, 13 May 2026 14:10:56 +0200 [thread overview]
Message-ID: <20260513121205.45921-1-jnilo@free.fr> (raw)
In-Reply-To: <3439217b-90b5-5d21-e777-d238b3ffc1a0@linux.intel.com>
On Wed, 13 May 2026, Ilpo Järvinen wrote:
> > +DEFINE_LOCK_GUARD_1(uart_port_lock_sysrq_irqsave, struct uart_port,
>
> I suppose the "check" in the name is kind of important detail so maybe
> it shouldn't be dropped from the guard name.
Quick clarification before I respin: do you want this renamed in v2?
I dropped the "check_" segment because the existing
guard(uart_port_lock_irqsave) doesn't mirror its destructor's name
either (it expands to uart_port_unlock_irqrestore, not
uart_port_lock_irqsave_and_unlock_irqrestore), and the longer
uart_port_lock_check_sysrq_irqsave starts to feel verbose. But I see
the symmetry argument with uart_unlock_and_check_sysrq_irqrestore() and
I have no strong attachment to the shorter name.
If you'd like the rename, I'll do it for v2. If you're fine either
way, I'll keep the current name -- patches 2/3 and 3/3 already have
your Reviewed-by trailers on the call sites and I'd rather not
invalidate those over a naming choice.
The other points (commit-message reflow, Cc: stable on 1/3,
single-line destructor formatting) are unambiguous and will land in
v2 regardless.
Thanks for the review.
--
Jacques
next prev parent reply other threads:[~2026-05-13 12:12 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-12 12:38 [REPORT] serial: 8250: BREAK + SysRq dispatch silently broken since 8324a54f604d Jacques Nilo
2026-05-12 12:58 ` Ilpo Järvinen
2026-05-12 13:06 ` Jacques Nilo
2026-05-12 13:21 ` Ilpo Järvinen
2026-05-12 13:46 ` [PATCH 0/3] serial: 8250: fix BREAK+SysRq dispatch on guard()-locked IRQ handlers Jacques Nilo
2026-05-12 13:46 ` [PATCH 1/3] serial: core: introduce guard(uart_port_lock_sysrq_irqsave) Jacques Nilo
2026-05-13 12:01 ` Ilpo Järvinen
2026-05-13 12:10 ` Jacques Nilo [this message]
2026-05-13 12:21 ` Ilpo Järvinen
2026-05-12 13:46 ` [PATCH 2/3] serial: 8250: dispatch SysRq character in serial8250_handle_irq() Jacques Nilo
2026-05-13 11:49 ` Ilpo Järvinen
2026-05-12 13:46 ` [PATCH 3/3] serial: 8250_dw: dispatch SysRq character in dw8250_handle_irq() Jacques Nilo
2026-05-13 11:50 ` Ilpo Järvinen
2026-05-13 13:30 ` [PATCH v2 0/3] serial: 8250: fix BREAK+SysRq dispatch on guard()-locked IRQ handlers Jacques Nilo
2026-05-13 13:30 ` [PATCH v2 1/3] serial: core: introduce guard(uart_port_lock_check_sysrq_irqsave) Jacques Nilo
2026-05-13 13:35 ` Ilpo Järvinen
2026-05-13 13:30 ` [PATCH v2 2/3] serial: 8250: dispatch SysRq character in serial8250_handle_irq() Jacques Nilo
2026-05-13 13:30 ` [PATCH v2 3/3] serial: 8250_dw: dispatch SysRq character in dw8250_handle_irq() Jacques Nilo
2026-05-13 17:51 ` [PATCH v2 0/3] serial: 8250: fix BREAK+SysRq dispatch on guard()-locked IRQ handlers Andy Shevchenko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260513121205.45921-1-jnilo@free.fr \
--to=jnilo@free.fr \
--cc=andriy.shevchenko@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=jirislaby@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox