From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Ajay Kaher <ajay.kaher@broadcom.com>, Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH v6.1.y 2/2] drm/ttm: Print the memory decryption status just once
Date: Mon, 9 Dec 2024 09:35:45 -0500 [thread overview]
Message-ID: <20241209082853-3b9d771658d7cddd@stable.kernel.org> (raw)
In-Reply-To: <20241209094904.2547579-3-ajay.kaher@broadcom.com>
[ Sasha's backport helper bot ]
Hi,
The upstream commit SHA1 provided is correct: 27906e5d78248b19bcdfdae72049338c828897bb
WARNING: Author mismatch between patch and upstream commit:
Backport author: Ajay Kaher <ajay.kaher@broadcom.com>
Commit author: Zack Rusin <zack.rusin@broadcom.com>
Status in newer kernel trees:
6.12.y | Present (exact SHA1)
6.6.y | Present (different SHA1: 306e99777886)
6.1.y | Not found
Note: The patch differs from the upstream commit:
---
Failed to apply patch cleanly, falling back to interdiff...
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-6.1.y | Success | Success |
next prev parent reply other threads:[~2024-12-09 14:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-09 9:49 [PATCH v6.1.y 0/2] drm/ttm: fixes for vmwgfx when SEV enabled Ajay Kaher
2024-12-09 9:49 ` [PATCH v6.1.y 1/2] drm/ttm: Make sure the mapped tt pages are decrypted when needed Ajay Kaher
2024-12-09 14:35 ` Sasha Levin
2024-12-12 12:40 ` Patch "drm/ttm: Make sure the mapped tt pages are decrypted when needed" has been added to the 6.1-stable tree gregkh
2024-12-09 9:49 ` [PATCH v6.1.y 2/2] drm/ttm: Print the memory decryption status just once Ajay Kaher
2024-12-09 14:35 ` Sasha Levin [this message]
2024-12-12 12:40 ` Patch "drm/ttm: Print the memory decryption status just once" has been added to the 6.1-stable tree gregkh
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=20241209082853-3b9d771658d7cddd@stable.kernel.org \
--to=sashal@kernel.org \
--cc=ajay.kaher@broadcom.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.