From: Jiri Slaby <jirislaby@kernel.org>
To: Dmitry Antipov <dmantipov@yandex.ru>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-serial@vger.kernel.org, lvc-project@linuxtesting.org
Subject: Re: [PATCH 2/2] tty: n_gsm: issue mutex_destroy() from gsm_dlci_free()
Date: Tue, 7 Jul 2026 05:24:57 +0200 [thread overview]
Message-ID: <eca3dbd4-802e-4bf7-85c2-db3d24792f7f@kernel.org> (raw)
In-Reply-To: <20260706142016.3385636-2-dmantipov@yandex.ru>
On 06. 07. 26, 16:20, Dmitry Antipov wrote:
> Although a no-op unless CONFIG_DEBUG_MUTEXES is enabled, add
> missing call to 'mutex_destroy()' in 'gsm_dlci_free()'.
You somehow omitted the "why" part.
thanks,
--
js
suse labs
next prev parent reply other threads:[~2026-07-07 3:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-06 14:20 [PATCH 1/2] tty: n_gsm: avoid reactivation without previous cleanup Dmitry Antipov
2026-07-06 14:20 ` [PATCH 2/2] tty: n_gsm: issue mutex_destroy() from gsm_dlci_free() Dmitry Antipov
2026-07-07 3:24 ` Jiri Slaby [this message]
2026-07-06 14:35 ` [PATCH 1/2] tty: n_gsm: avoid reactivation without previous cleanup Greg Kroah-Hartman
2026-07-06 14:49 ` Dmitry Antipov
2026-07-06 15:18 ` Greg Kroah-Hartman
2026-07-07 5:47 ` Dmitry Antipov
2026-07-07 5:58 ` Greg Kroah-Hartman
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=eca3dbd4-802e-4bf7-85c2-db3d24792f7f@kernel.org \
--to=jirislaby@kernel.org \
--cc=dmantipov@yandex.ru \
--cc=gregkh@linuxfoundation.org \
--cc=linux-serial@vger.kernel.org \
--cc=lvc-project@linuxtesting.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