The patch titled
Subject: rtc: add support of rtc-mv for MVEBU SoCs
has been added to the -mm tree. Its filename is
rtc-add-support-of-rtc-mv-for-mvebu-socs.patch
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b) Prefer to cc a suitable mailing list as well
c) Ideally: find the original patch on the mailing list and do a
reply-to-all to that, adding suitable additional cc's
*** Remember to use Documentation/SubmitChecklist when testing your code ***
The -mm tree is included into linux-next and is updated
there every 3-4 working days
------------------------------------------------------
From: Gregory CLEMENT <gregory.clement@xxxxxxxxxxxxxxxxxx>
Subject: rtc: add support of rtc-mv for MVEBU SoCs
The Armada 370 and Armada XP Socs have the same controller that the one
used in the orion platforms. This patch enables the selection of rtc-mv
with mvebu platforms.
Signed-off-by: Gregory CLEMENT <gregory.clement@xxxxxxxxxxxxxxxxxx>
Acked-by: Andrew Lunn <andrew@xxxxxxx>
Cc: Russell King <linux@xxxxxxxxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
drivers/rtc/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff -puN drivers/rtc/Kconfig~rtc-add-support-of-rtc-mv-for-mvebu-socs drivers/rtc/Kconfig
--- a/drivers/rtc/Kconfig~rtc-add-support-of-rtc-mv-for-mvebu-socs
+++ a/drivers/rtc/Kconfig
@@ -1055,7 +1055,7 @@ config RTC_DRV_TX4939
config RTC_DRV_MV
tristate "Marvell SoC RTC"
- depends on ARCH_KIRKWOOD || ARCH_DOVE
+ depends on ARCH_KIRKWOOD || ARCH_DOVE || ARCH_MVEBU
help
If you say yes here you will get support for the in-chip RTC
that can be found in some of Marvell's SoC devices, such as
_
Patches currently in -mm which might be from gregory.clement@xxxxxxxxxxxxxxxxxx are
linux-next.patch
rtc-add-support-of-rtc-mv-for-mvebu-socs.patch
arm-mvebu-add-rtc-support-for-armada-370-and-armada-xp.patch
arm-mvebu-update-defconfig-with-marvell-rtc-support.patch
--
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
