From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org, aurabindo.pillai@amd.com
Cc: Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 6.1.y] drm/amd/display: should support dmub hw lock on Replay
Date: Tue, 25 Mar 2025 07:33:27 -0400 [thread overview]
Message-ID: <20250324234654-d463f40a9a48609e@stable.kernel.org> (raw)
In-Reply-To: <20250324164929.2622811-1-aurabindo.pillai@amd.com>
[ 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: bfeefe6ea5f18cabb8fda55364079573804623f9
WARNING: Author mismatch between patch and found commit:
Backport author: Aurabindo Pillai<aurabindo.pillai@amd.com>
Commit author: Martin Tsai<martin.tsai@amd.com>
Status in newer kernel trees:
6.13.y | Present (exact SHA1)
6.12.y | Present (exact SHA1)
6.6.y | Not found
Note: The patch differs from the upstream commit:
---
1: bfeefe6ea5f18 < -: ------------- drm/amd/display: should support dmub hw lock on Replay
-: ------------- > 1: 344a09659766c Linux 6.1.131
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-6.1.y | Success | Success |
prev parent reply other threads:[~2025-03-25 11:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-24 16:20 FAILED: patch "[PATCH] drm/amd/display: should support dmub hw lock on Replay" failed to apply to 6.1-stable tree gregkh
2025-03-24 16:49 ` [PATCH 6.1.y] drm/amd/display: should support dmub hw lock on Replay Aurabindo Pillai
2025-03-24 18:34 ` Greg KH
2025-03-24 19:06 ` Pillai, Aurabindo
2025-03-25 11:33 ` Sasha Levin [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=20250324234654-d463f40a9a48609e@stable.kernel.org \
--to=sashal@kernel.org \
--cc=aurabindo.pillai@amd.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.