From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Donglin Peng <dolinux.peng@gmail.com>
Cc: javier.carrasco.cruz@gmail.com, kees@kernel.org,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Input: ims-pcu - fix a mutex usage error
Date: Sun, 22 Sep 2024 00:58:47 -0700 [thread overview]
Message-ID: <Zu_ONyU6H0dZBKB-@google.com> (raw)
In-Reply-To: <20240921071501.263450-1-dolinux.peng@gmail.com>
Hi Donglin,
On Sat, Sep 21, 2024 at 03:15:01PM +0800, Donglin Peng wrote:
> The mutex_lock_interruptible should be switched to scoped_cond_guard(mutex_intr, ...)
> instead of scoped_cond_guard(mutex, ..).
Thank you for the patch but I already got a fix for this issue:
https://lore.kernel.org/r/20240910-input-misc-ims-pcu-fix-mutex-intr-v1-1-bdd983685c43@baylibre.com
Thanks.
--
Dmitry
prev parent reply other threads:[~2024-09-22 7:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-21 7:15 [PATCH] Input: ims-pcu - fix a mutex usage error Donglin Peng
2024-09-22 7:58 ` Dmitry Torokhov [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=Zu_ONyU6H0dZBKB-@google.com \
--to=dmitry.torokhov@gmail.com \
--cc=dolinux.peng@gmail.com \
--cc=javier.carrasco.cruz@gmail.com \
--cc=kees@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).