[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20190107175911.GA11863@lakrids.cambridge.arm.com>
Date: Mon, 7 Jan 2019 17:59:11 +0000
From: Mark Rutland <mark.rutland@....com>
To: Mark Brown <broonie@...nel.org>
Cc: Anders Roxell <anders.roxell@...aro.org>,
linux-kernel@...r.kernel.org, catalin.marinas@....com,
will.deacon@....com, arnd@...db.de, mingo@...hat.com,
rostedt@...dmis.org, akpm@...ux-foundation.org
Subject: Re: [RFC PATCH 3/3] arm64: add a new config option KTEST_RUNNABLE
On Mon, Jan 07, 2019 at 05:55:31PM +0000, Mark Brown wrote:
> On Mon, Jan 07, 2019 at 02:43:57PM +0000, Mark Rutland wrote:
>
> > Is it possible to use an allyesconfig rather than an allmodconfig? That
> > would leave all relevant options built-in.
>
> The allyesconfig would make it more difficult to apply this approach to
> real hardware which is part of the goal here - the idea was to come up
> with a way of making runnable configurations which are likely to be
> usable with random userspace testsuites in order to avoid needing ever
> expanding combinations of builds.
Ok.
Is it somehow possible to fuse defconfig with an allmodconfig, with
defconfig's CONFIG_FOO=y taking precedence over allmodconfig's
CONFIG_FOO=m?
IIUC, that would give you the necessary platform bits, at least for
anything supported by defconfig. That would also happen to get
CONFIG_UNIX=y, too.
Thanks,
Mark.
Powered by blists - more mailing lists