[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20191202211844.19629-1-enric.balletbo@collabora.com>
Date: Mon, 2 Dec 2019 22:18:42 +0100
From: Enric Balletbo i Serra <enric.balletbo@...labora.com>
To: linux-kernel@...r.kernel.org
Cc: Collabora Kernel ML <kernel@...labora.com>, groeck@...omium.org,
bleung@...omium.org, dtor@...omium.org,
fabien.lahoudere@...labora.com, guillaume.tucker@...labora.com,
"H. Peter Anvin" <hpa@...or.com>, Borislav Petkov <bp@...en8.de>,
x86@...nel.org, Thomas Gleixner <tglx@...utronix.de>,
Krzysztof Kozlowski <krzk@...nel.org>,
Ingo Molnar <mingo@...hat.com>,
"Ahmed S. Darwish" <darwish.07@...il.com>,
Geert Uytterhoeven <geert+renesas@...der.be>,
Alexey Brodkin <alexey.brodkin@...opsys.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Ard Biesheuvel <ardb@...nel.org>
Subject: [PATCH 0/2] Standard x86_64 defconfig for KernelCI or Chromebooks
Hi x86 maintainers,
For testing purposes it'd be useful have a standard/mainline config that
supports the devices that we're testing in KernelCI. For Chromebooks we
try to take care of have multi_v7_defconfig and arm64 defconfig up to
date supporting different devices, that way, we don't need to deal with
out-of-tree kernel configs or fragments. We'd like to do the same for
x86 architecture, hence this patch series.
I am unsure if the x86_64_defconfig is the right place to do it, if not,
maybe we can add a chromebooks.config (like xen.config) or even better,
a kernelci.config, so take this as a RFC if that's the case.
Thanks,
Enric Balletbo i Serra (2):
x86_64_defconfig: Normalize x86_64 defconfig
x86_64_defconfig: Enable support for Chromebooks devices
arch/x86/configs/x86_64_defconfig | 156 +++++++++++++++++++-----------
1 file changed, 97 insertions(+), 59 deletions(-)
--
2.20.1
Powered by blists - more mailing lists