[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190107175531.GN9570@sirena.org.uk>
Date: Mon, 7 Jan 2019 17:55:31 +0000
From: Mark Brown <broonie@...nel.org>
To: Mark Rutland <mark.rutland@....com>
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 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.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists