Re: FAILED: patch "[PATCH] ARM: dts: omap3-tao3530: Fix incorrect MMC card detection" failed to apply to 4.9-stable tree

[Sasha Levin <sashal@kernel.org>]

On Sun, Dec 15, 2019 at 02:33:31PM +0100, gregkh@linuxfoundation.org wrote:
>
>The patch below does not apply to the 4.9-stable tree.
>If someone wants it applied there, or to any other stable or longterm
>tree, then please email the backport, including the original git commit
>id to <stable@vger.kernel.org>.
>
>thanks,
>
>greg k-h
>
>------------------ original commit in Linus's tree ------------------
>
>From 287897f9aaa2ad1c923d9875914f57c4dc9159c8 Mon Sep 17 00:00:00 2001
>From: Jarkko Nikula <jarkko.nikula@bitmer.com>
>Date: Sat, 16 Nov 2019 17:16:51 +0200
>Subject: [PATCH] ARM: dts: omap3-tao3530: Fix incorrect MMC card detection
> GPIO polarity
>
>The MMC card detection GPIO polarity is active low on TAO3530, like in many
>other similar boards. Now the card is not detected and it is unable to
>mount rootfs from an SD card.
>
>Fix this by using the correct polarity.
>
>This incorrect polarity was defined already in the commit 30d95c6d7092
>("ARM: dts: omap3: Add Technexion TAO3530 SOM omap3-tao3530.dtsi") in v3.18
>kernel and later changed to use defined GPIO constants in v4.4 kernel by
>the commit 3a637e008e54 ("ARM: dts: Use defined GPIO constants in flags
>cell for OMAP2+ boards").
>
>While the latter commit did not introduce the issue I'm marking it with
>Fixes tag due the v4.4 kernels still being maintained.
>
>Fixes: 3a637e008e54 ("ARM: dts: Use defined GPIO constants in flags cell for OMAP2+ boards")
>Cc: linux-stable <stable@vger.kernel.org> # 4.4+
>Signed-off-by: Jarkko Nikula <jarkko.nikula@bitmer.com>
>Signed-off-by: Tony Lindgren <tony@atomide.com>

Fixed up context and queued for 4.9 and 4.4.

-- 
Thanks,
Sasha