[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CABGGisyOSc+Mh3rrEwazgayue7hqZtNuAxRt112VAhDTTEeDrQ@mail.gmail.com>
Date: Mon, 2 Jul 2018 21:16:27 -0600
From: Rob Herring <robh@...nel.org>
To: ren_guo@...ky.com
Cc: linux-arch@...r.kernel.org,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Thomas Gleixner <tglx@...utronix.de>,
Daniel Lezcano <daniel.lezcano@...aro.org>,
Jason Cooper <jason@...edaemon.net>,
Arnd Bergmann <arnd@...db.de>, c-sky_gcc_upstream@...ky.com,
gnu-csky@...tor.com, thomas.petazzoni@...tlin.com,
wbx@...ibc-ng.org, Greentime Hu <green.hu@...il.com>
Subject: Re: [PATCH V2 02/19] csky: defconfig
On Sun, Jul 1, 2018 at 11:34 AM Guo Ren <ren_guo@...ky.com> wrote:
>
Needs a commit msg. Perhaps some overview of what's in each config.
> Signed-off-by: Guo Ren <ren_guo@...ky.com>
> ---
> arch/csky/configs/gx66xx_defconfig | 549 +++++++++++++++++++++++++++++++++
> arch/csky/configs/qemu_ck807_defconfig | 541 ++++++++++++++++++++++++++++++++
> 2 files changed, 1090 insertions(+)
> create mode 100644 arch/csky/configs/gx66xx_defconfig
> create mode 100644 arch/csky/configs/qemu_ck807_defconfig
Are these configs mutually exclusive? We try to have one kernel build
serve many platforms. So you'd probably want to divide things between
the 2 ABIs.
It looks like you still have lots of options enabled that I wouldn't
expect you to need. Start with something more minimal for what you
need to boot and support upstream.
For a full config, you can use allmodconfig at least to build test.
Rob
Powered by blists - more mailing lists