The patch titled Subject: arm: mvebu: update defconfig with Marvell RTC support has been added to the -mm tree. Its filename is arm-mvebu-update-defconfig-with-marvell-rtc-support.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: arm: mvebu: update defconfig with Marvell RTC support The RTC class driver is already part of the mvebu_defconfig but the Marvell internal RTC not yet. Now that its support is added for mvebu let's update the config file. Signed-off-by: Gregory CLEMENT <gregory.clement@xxxxxxxxxxxxxxxxxx> Cc: Andrew Lunn <andrew@xxxxxxx> Cc: Russell King <linux@xxxxxxxxxxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> --- arch/arm/configs/mvebu_defconfig | 1 + 1 file changed, 1 insertion(+) diff -puN arch/arm/configs/mvebu_defconfig~arm-mvebu-update-defconfig-with-marvell-rtc-support arch/arm/configs/mvebu_defconfig --- a/arch/arm/configs/mvebu_defconfig~arm-mvebu-update-defconfig-with-marvell-rtc-support +++ a/arch/arm/configs/mvebu_defconfig @@ -39,6 +39,7 @@ CONFIG_GPIO_SYSFS=y # CONFIG_USB_SUPPORT is not set CONFIG_RTC_CLASS=y CONFIG_RTC_DRV_S35390A=y +CONFIG_RTC_DRV_MV=y CONFIG_DMADEVICES=y CONFIG_MV_XOR=y # CONFIG_IOMMU_SUPPORT is not set _ 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