This is a note to let you know that I've just added the patch titled
ARM: dts: orion5x: fix number of sata port for linkstation ls-gl
to the 4.8-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
arm-dts-orion5x-fix-number-of-sata-port-for-linkstation-ls-gl.patch
and it can be found in the queue-4.8 subdirectory.
If you, or anyone else, feels it should not be added to the stable tree,
please let <stable@xxxxxxxxxxxxxxx> know about it.
>From 038ccb3e8cee52e07dc118ff99f47eaebc1d0746 Mon Sep 17 00:00:00 2001
From: Roger Shimizu <rogershimizu@xxxxxxxxx>
Date: Fri, 2 Dec 2016 00:11:12 +0900
Subject: ARM: dts: orion5x: fix number of sata port for linkstation ls-gl
From: Roger Shimizu <rogershimizu@xxxxxxxxx>
commit 038ccb3e8cee52e07dc118ff99f47eaebc1d0746 upstream.
Bug report from Debian [0] shows there's minor changed model of
Linkstation LS-GL that uses the 2nd SATA port of the SoC.
So it's necessary to enable two SATA ports, though for that specific
model only the 2nd one is used.
[0] https://bugs.debian.org/845611
Fixes: b1742ffa9ddb ("ARM: dts: orion5x: add device tree for buffalo linkstation ls-gl")
Reported-by: Ryan Tandy <ryan@xxxxxxxxx>
Tested-by: Ryan Tandy <ryan@xxxxxxxxx>
Signed-off-by: Roger Shimizu <rogershimizu@xxxxxxxxx>
Signed-off-by: Gregory CLEMENT <gregory.clement@xxxxxxxxxxxxxxxxxx>
Signed-off-by: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
---
arch/arm/boot/dts/orion5x-linkstation-lsgl.dts | 4 ++++
1 file changed, 4 insertions(+)
--- a/arch/arm/boot/dts/orion5x-linkstation-lsgl.dts
+++ b/arch/arm/boot/dts/orion5x-linkstation-lsgl.dts
@@ -82,6 +82,10 @@
gpios = <&gpio0 9 GPIO_ACTIVE_HIGH>;
};
+&sata {
+ nr-ports = <2>;
+};
+
&ehci1 {
status = "okay";
};
Patches currently in stable-queue which might be from rogershimizu@xxxxxxxxx are
queue-4.8/arm-dts-orion5x-fix-number-of-sata-port-for-linkstation-ls-gl.patch
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html