From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org, stable-commits@vger.kernel.org,
dlechner@baylibre.com
Subject: Re: Patch "Input: ims-pcu - fix calling interruptible mutex" has been added to the 6.11-stable tree
Date: Tue, 1 Oct 2024 03:41:49 -0700 [thread overview]
Message-ID: <ZvvR7d_IaOhAeRv9@google.com> (raw)
In-Reply-To: <2024100130-stereo-diner-11ba@gregkh>
On Tue, Oct 01, 2024 at 11:33:12AM +0200, Greg KH wrote:
> On Tue, Oct 01, 2024 at 02:07:21AM -0700, Dmitry Torokhov wrote:
> > On Mon, Sep 30, 2024 at 07:24:28PM -0400, Sasha Levin wrote:
> > > This is a note to let you know that I've just added the patch titled
> > >
> > > Input: ims-pcu - fix calling interruptible mutex
> > >
> > > to the 6.11-stable tree which can be found at:
> > > http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
> > >
> > > The filename of the patch is:
> > > input-ims-pcu-fix-calling-interruptible-mutex.patch
> > > and it can be found in the queue-6.11 subdirectory.
> > >
> > > If you, or anyone else, feels it should not be added to the stable tree,
> > > please let <stable@vger.kernel.org> know about it.
> > >
> >
> > Did you manage to pick up 703f12672e1f ("Input: ims-pcu - switch to
> > using cleanup functions") for stable? I would love to see the
> > justification for that...
>
> It already is in the 6.11 kernel tree, so why would this fix, which
> says:
>
> > > commit c137195362a652adfbc6a538b78a40b043de6eb0
> > > Author: David Lechner <dlechner@baylibre.com>
> > > Date: Tue Sep 10 16:58:47 2024 -0500
> > >
> > > Input: ims-pcu - fix calling interruptible mutex
> > >
> > > [ Upstream commit 82abef590eb31d373e632743262ee7c42f49c289 ]
> > >
> > > Fix calling scoped_cond_guard() with mutex instead of mutex_intr.
> > >
> > > scoped_cond_guard(mutex, ...) will call mutex_lock() instead of
> > > mutex_lock_interruptible().
> > >
> > > Fixes: 703f12672e1f ("Input: ims-pcu - switch to using cleanup functions")
>
> This is a bugfix for the 6.11 tree, not be applicable to the 6.11.y
> releases?
Oh, my bad, I did not realize 703f12672e1f made into 6.11. Sorry about
this.
--
Dmitry
prev parent reply other threads:[~2024-10-01 10:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240930232429.2569091-1-sashal@kernel.org>
2024-10-01 9:07 ` Patch "Input: ims-pcu - fix calling interruptible mutex" has been added to the 6.11-stable tree Dmitry Torokhov
2024-10-01 9:33 ` Greg KH
2024-10-01 10:41 ` 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=ZvvR7d_IaOhAeRv9@google.com \
--to=dmitry.torokhov@gmail.com \
--cc=dlechner@baylibre.com \
--cc=gregkh@linuxfoundation.org \
--cc=stable-commits@vger.kernel.org \
--cc=stable@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).