From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Andy-ld Lu <andy-ld.lu@mediatek.com>, Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 6.6.y] mmc: mtk-sd: Fix MMC_CAP2_CRYPTO flag setting
Date: Mon, 9 Dec 2024 09:35:37 -0500 [thread overview]
Message-ID: <20241208093511-fd8981455f4e690f@stable.kernel.org> (raw)
In-Reply-To: <20241208090347.22418-1-andy-ld.lu@mediatek.com>
[ Sasha's backport helper bot ]
Hi,
Found matching upstream commit: 2508925fb346661bad9f50b497d7ac7d0b6085d0
Status in newer kernel trees:
6.12.y | Present (different SHA1: 6b751bd44d86)
6.6.y | Present (different SHA1: 8a68eb7a528c)
Note: The patch differs from the upstream commit:
---
1: 2508925fb3466 < -: ------------- mmc: mtk-sd: Fix MMC_CAP2_CRYPTO flag setting
-: ------------- > 1: 0b11ccaf21e40 mmc: mtk-sd: Fix MMC_CAP2_CRYPTO flag setting
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-6.6.y | Success | Success |
prev parent reply other threads:[~2024-12-09 14:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-06 10:11 FAILED: patch "[PATCH] mmc: mtk-sd: Fix MMC_CAP2_CRYPTO flag setting" failed to apply to 6.6-stable tree gregkh
2024-12-08 9:03 ` [PATCH 6.6.y] mmc: mtk-sd: Fix MMC_CAP2_CRYPTO flag setting Andy-ld Lu
2024-12-09 14:35 ` 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=20241208093511-fd8981455f4e690f@stable.kernel.org \
--to=sashal@kernel.org \
--cc=andy-ld.lu@mediatek.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.