ARM: multi_v7_defconfig: add driver support for hix5hd2
PATCH 1/1 ARM: multi_v7_defconfig: add driver support for hix5hd2
Tested on hix5hd2 platform with mmc, usb, network, reboot etc.
--- arch/arm/configs/multi_v7_defconfig | 7 +++++++ 1 file changed, 7 insertions(+)
arch/arm/configs/multi_v7_defconfig +7 -0
@@ -10,6 +10,7 @@ CONFIG_PERF_EVENTS=y CONFIG_MODULES=y CONFIG_MODULE_UNLOAD=y CONFIG_PARTITION_ADVANCED=y +CONFIG_CMDLINE_PARTITION=y CONFIG_ARCH_VIRT=y CONFIG_ARCH_MVEBU=y CONFIG_MACH_ARMADA_370=y
@@ -153,6 +154,7 @@ CONFIG_AHCI_TEGRA=y CONFIG_SATA_HIGHBANK=y CONFIG_SATA_MV=y CONFIG_NETDEVICES=y +CONFIG_HIX5HD2_GMAC=y CONFIG_SUN4I_EMAC=y CONFIG_MACB=y CONFIG_NET_CALXEDA_XGMAC=y
@@ -289,6 +291,8 @@ CONFIG_REGULATOR_AB8500=y CONFIG_REGULATOR_AS3722=y CONFIG_REGULATOR_BCM590XX=y CONFIG_REGULATOR_GPIO=y +CONFIG_MFD_SYSCON=y +CONFIG_POWER_RESET_SYSCON=y CONFIG_REGULATOR_MAX8907=y CONFIG_REGULATOR_PALMAS=y CONFIG_REGULATOR_S2MPS11=y
@@ -369,6 +373,8 @@ CONFIG_MMC_OMAP_HS=y CONFIG_MMC_MVSDIO=y CONFIG_MMC_SUNXI=y CONFIG_MMC_DW=y +CONFIG_MMC_DW_IDMAC=y +CONFIG_MMC_DW_PLTFM=y CONFIG_MMC_DW_EXYNOS=y CONFIG_MMC_DW_ROCKCHIP=y CONFIG_NEW_LEDS=y
@@ -440,6 +446,7 @@ CONFIG_AK8975=y CONFIG_PWM=y CONFIG_PWM_TEGRA=y CONFIG_PWM_VT8500=y +CONFIG_PHY_HIX5HD2_SATA=y CONFIG_OMAP_USB2=y CONFIG_TI_PIPE3=y CONFIG_PHY_MIPHY365X=y
Signature · 1 line
1.7.9.5
Arnd Bergmann
AppliedPATCH 1/1 ARM: multi_v7_defconfig: add driver support for hix5hd2
Quoted 3 lines · Zhangfei Gao
Tested on hix5hd2 platform with mmc, usb, network, reboot etc.
Signed-off-by Zhangfei Gao <[email protected]>
Applied to next/defconfig, thanks!
You mentioned earlier that you'd like me to apply this patch so I took it, but you did not send it to arm at kernel.org or ask for it to be applied in the email, so there was still a chance for it to get lost. Please try to be explict about these things as you can.
Arnd
PATCH 1/1 ARM: multi_v7_defconfig: add driver support for hix5hd2
Quoted 12 lines · Arnd Bergmann
Quoted 3 lines · Zhangfei Gao
Tested on hix5hd2 platform with mmc, usb, network, reboot etc.
Signed-off-by Zhangfei Gao <[email protected]>Applied to next/defconfig, thanks!
You mentioned earlier that you'd like me to apply this patch so I took it, but you did not send it to arm at kernel.org or ask for it to be applied in the email, so there was still a chance for it to get lost. Please try to be explict about these things as you can.
Thanks Arnd
Usually, should this info be listed in the git msg or reply with the original patch?
Thanks
PATCH 1/1 ARM: multi_v7_defconfig: add driver support for hix5hd2
Quoted 14 lines · On Friday 28 November 2014 23:15:48 zhangfei wrote:
Quoted 12 lines · Arnd Bergmann
Quoted 3 lines · Zhangfei Gao
Tested on hix5hd2 platform with mmc, usb, network, reboot etc.
Signed-off-by Zhangfei Gao <[email protected]>Applied to next/defconfig, thanks!
You mentioned earlier that you'd like me to apply this patch so I took it, but you did not send it to arm at kernel.org or ask for it to be applied in the email, so there was still a chance for it to get lost. Please try to be explict about these things as you can.
Quoted 4 lines
Thanks Arnd
Usually, should this info be listed in the git msg or reply with the original patch?
The best way to do this is to put it under the '---' line that separates the changelog part of the patch from the additional info like the diffstat.
If you are sending more than one patch at once, use a [PATCH 0/x] introductory mail and put it in there.
Arnd
PATCH 1/1 ARM: multi_v7_defconfig: add driver support for hix5hd2
Quoted 17 lines · Arnd Bergmann
Quoted 16 lines · On Friday 28 November 2014 23:15:48 zhangfei wrote:
Quoted 12 lines · Arnd Bergmann
Quoted 3 lines · Zhangfei Gao
Tested on hix5hd2 platform with mmc, usb, network, reboot etc.
Signed-off-by Zhangfei Gao <[email protected]>Applied to next/defconfig, thanks!
You mentioned earlier that you'd like me to apply this patch so I took it, but you did not send it to arm at kernel.org or ask for it to be applied in the email, so there was still a chance for it to get lost. Please try to be explict about these things as you can.
Thanks Arnd
Quoted 9 lines
Quoted 2 lines
Usually, should this info be listed in the git msg or reply with the original patch?
The best way to do this is to put it under the '---' line that separates the changelog part of the patch from the additional info like the diffstat.
If you are sending more than one patch at once, use a [PATCH 0/x] introductory mail and put it in there.
Thanks Arnd for the kind education.