From: Evgeny Pimenov <pimenoveu12@gmail.com>
To: Sasha Levin <sashal@kernel.org>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH 6.1.y] ASoC: qcom: Fix sc7280 lpass potential buffer overflow
Date: Tue, 22 Apr 2025 22:59:31 +0300 [thread overview]
Message-ID: <20250422225931.7c3101ff@parrot> (raw)
In-Reply-To: <20250421193020-123e6255cd3f396a@stable.kernel.org>
On Mon, 21 Apr 2025 22:15: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
>
> Found matching upstream commit: a31a4934b31faea76e735bab17e63d02fcd8e029
This founded upstream commit is correct.
>
> Status in newer kernel trees:
> 6.14.y | Not found
> 6.12.y | Not found
> 6.6.y | Not found
>
> Note: The patch differs from the upstream commit:
> ---
> 1: a31a4934b31fa < -: ------------- ASoC: qcom: Fix sc7280 lpass potential buffer overflow
> -: ------------- > 1: 420102835862f Linux 6.1.134
> ---
>
> Results of testing on various branches:
>
> | Branch | Patch Apply | Build Test |
> |---------------------------|-------------|------------|
> | stable/linux-6.1.y | Success | Success |
prev parent reply other threads:[~2025-04-22 19:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-21 11:49 FAILED: patch "[PATCH] ASoC: qcom: Fix sc7280 lpass potential buffer overflow" failed to apply to 6.1-stable tree gregkh
2025-04-21 19:37 ` [PATCH 6.1.y] ASoC: qcom: Fix sc7280 lpass potential buffer overflow Evgeny Pimenov
2025-04-22 2:15 ` Sasha Levin
2025-04-22 19:59 ` Evgeny Pimenov [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=20250422225931.7c3101ff@parrot \
--to=pimenoveu12@gmail.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