From: Luca Ceresoli <luca.ceresoli@bootlin.com>
To: Sasha Levin <sashal@kernel.org>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH 6.12.y] iio: light: opt3001: fix deadlock due to concurrent flag access
Date: Fri, 16 May 2025 20:43:31 +0200 [thread overview]
Message-ID: <20250516204331.15c72a9b@booty> (raw)
In-Reply-To: <20250516112545-f4b2ef15e27e8b30@stable.kernel.org>
On Fri, 16 May 2025 14:26:41 -0400
Sasha Levin <sashal@kernel.org> wrote:
> [ Sasha's backport helper bot ]
>
> Hi,
>
> Summary of potential issues:
> ⚠️ Found matching upstream commit but patch is missing proper reference to it
Apologies, I had missed the [ Upstream commit <sha> ].
Sent v2.
Luca
--
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2025-05-16 18:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-12 10:05 FAILED: patch "[PATCH] iio: light: opt3001: fix deadlock due to concurrent flag" failed to apply to 6.12-stable tree gregkh
2025-05-15 20:21 ` [PATCH 6.12.y] iio: light: opt3001: fix deadlock due to concurrent flag access Luca Ceresoli
2025-05-16 18:26 ` Sasha Levin
2025-05-16 18:43 ` Luca Ceresoli [this message]
2025-05-16 18:41 ` [PATCH 6.12.y v2] " Luca Ceresoli
2025-05-17 13:08 ` Sasha Levin
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=20250516204331.15c72a9b@booty \
--to=luca.ceresoli@bootlin.com \
--cc=sashal@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