From: Jiri Slaby <jirislaby@kernel.org>
To: John de la Garza <john@jjdev.com>, gregkh@linuxfoundation.org
Cc: linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tty: tty_jobctrl: use guard()s in tiocspgrp()
Date: Wed, 1 Jul 2026 06:11:27 +0200 [thread overview]
Message-ID: <7c9c4d2a-3778-4955-ac5d-1c54175d97dc@kernel.org> (raw)
In-Reply-To: <20260701030139.3189030-1-john@jjdev.com>
On 01. 07. 26, 5:27, John de la Garza wrote:
> Convert the manual spin_lock_irq()/rcu_read_lock() nesting in tiocspgrp()
> to scoped guard()s. This drops the out_unlock and out_unlock_ctrl labels
> and lets the error paths return directly.
>
> No functional change intended.
Nice cleanup!
Reviewed-by: Jiri Slaby <jirislaby@kernel.org>
> Signed-off-by: John de la Garza <john@jjdev.com>
thanks,
--
js
suse labs
prev parent reply other threads:[~2026-07-01 4:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-01 3:27 [PATCH] tty: tty_jobctrl: use guard()s in tiocspgrp() John de la Garza
2026-07-01 4:11 ` Jiri Slaby [this message]
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=7c9c4d2a-3778-4955-ac5d-1c54175d97dc@kernel.org \
--to=jirislaby@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=john@jjdev.com \
--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