From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Francesco Dolcini <francesco@dolcini.it>,
Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 6.1.y] arm64: dts: imx8mm: Drop sd-vsel-gpios from i.MX8M Mini Verdin SoM
Date: Tue, 3 Jun 2025 14:36:01 -0400 [thread overview]
Message-ID: <20250603134959-1f578cd8b4bcb4c2@stable.kernel.org> (raw)
In-Reply-To: <20250602155845.227354-1-francesco@dolcini.it>
[ Sasha's backport helper bot ]
Hi,
✅ All tests passed successfully. No issues detected.
No action required from the submitter.
The upstream commit SHA1 provided is correct: 8bad8c923f217d238ba4f1a6d19d761e53bfbd26
WARNING: Author mismatch between patch and upstream commit:
Backport author: Francesco Dolcini<francesco@dolcini.it>
Commit author: Marek Vasut<marex@denx.de>
Status in newer kernel trees:
6.15.y | Present (exact SHA1)
6.14.y | Present (exact SHA1)
6.12.y | Present (exact SHA1)
6.6.y | Present (exact SHA1)
Note: The patch differs from the upstream commit:
---
1: 8bad8c923f217 ! 1: a0da60f537dd7 arm64: dts: imx8mm: Drop sd-vsel-gpios from i.MX8M Mini Verdin SoM
@@ Metadata
## Commit message ##
arm64: dts: imx8mm: Drop sd-vsel-gpios from i.MX8M Mini Verdin SoM
+ [ Upstream commit 8bad8c923f217d238ba4f1a6d19d761e53bfbd26 ]
+
The VSELECT pin is configured as MX8MM_IOMUXC_GPIO1_IO04_USDHC2_VSELECT
and not as a GPIO, drop the bogus sd-vsel-gpios property as the eSDHC
block handles the VSELECT pin on its own.
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-6.1.y | Success | Success |
next prev parent reply other threads:[~2025-06-03 18:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-02 15:58 [PATCH 6.1.y] arm64: dts: imx8mm: Drop sd-vsel-gpios from i.MX8M Mini Verdin SoM Francesco Dolcini
2025-06-03 18:36 ` Sasha Levin [this message]
2025-06-04 13:24 ` Greg Kroah-Hartman
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=20250603134959-1f578cd8b4bcb4c2@stable.kernel.org \
--to=sashal@kernel.org \
--cc=francesco@dolcini.it \
--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.