[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAK8P3a0rwi=uDFYiF50e5HkYoDQUA6_VSWDMiAVeTMaRzeE6oQ@mail.gmail.com>
Date: Wed, 20 Feb 2019 10:28:38 +0100
From: Arnd Bergmann <arnd@...db.de>
To: Sugaya Taichi <sugaya.taichi@...ionext.com>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux ARM <linux-arm-kernel@...ts.infradead.org>,
soc@...nel.org, Takao Orito <orito.takao@...ionext.com>,
Kazuhiro Kasai <kasai.kazuhiro@...ionext.com>,
Shinji Kanematsu <kanematsu.shinji@...ionext.com>,
Jassi Brar <jaswinder.singh@...aro.org>,
Masami Hiramatsu <masami.hiramatsu@...aro.org>
Subject: Re: [PATCH v3 9/9] ARM: configs: Add Milbeaut M10V defconfig
On Wed, Feb 20, 2019 at 8:44 AM Sugaya Taichi
<sugaya.taichi@...ionext.com> wrote:
> diff --git a/arch/arm/configs/milbeaut_m10v_defconfig b/arch/arm/configs/milbeaut_m10v_defconfig
> new file mode 100644
> index 0000000..a263211
> --- /dev/null
> +++ b/arch/arm/configs/milbeaut_m10v_defconfig
> @@ -0,0 +1,175 @@
I no longer see anything here that should be turned off, but you
might want to run 'make savedefconfig' and use the output of that,
to make it easier to keep it up to date.
> diff --git a/arch/arm/configs/multi_v7_defconfig b/arch/arm/configs/multi_v7_defconfig
> index 5bee34a..6753805 100644
> --- a/arch/arm/configs/multi_v7_defconfig
> +++ b/arch/arm/configs/multi_v7_defconfig
> @@ -54,6 +54,8 @@ CONFIG_SOC_VF610=y
> CONFIG_ARCH_KEYSTONE=y
> CONFIG_ARCH_MEDIATEK=y
> CONFIG_ARCH_MESON=y
> +CONFIG_ARCH_MILBEAUT=y
> +CONFIG_ARCH_MILBEAUT_M10V=y
> CONFIG_ARCH_MVEBU=y
> CONFIG_MACH_ARMADA_370=y
> CONFIG_MACH_ARMADA_375=y
I'm surprised that you don't need to enable any drivers. Does this actually
boot on your hardware?
Arnd
Powered by blists - more mailing lists