From: Mark Rutland <mark.rutland@arm.com>
To: Mark Brown <broonie@kernel.org>
Cc: Anders Roxell <anders.roxell@linaro.org>,
linux-kernel@vger.kernel.org, catalin.marinas@arm.com,
will.deacon@arm.com, arnd@arndb.de, mingo@redhat.com,
rostedt@goodmis.org, akpm@linux-foundation.org
Subject: Re: [RFC PATCH 3/3] arm64: add a new config option KTEST_RUNNABLE
Date: Mon, 7 Jan 2019 17:59:11 +0000 [thread overview]
Message-ID: <20190107175911.GA11863@lakrids.cambridge.arm.com> (raw)
In-Reply-To: <20190107175531.GN9570@sirena.org.uk>
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.
prev parent reply other threads:[~2019-01-07 17:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-13 12:29 [RFC PATCH 0/3] Make allmodconfig boot in qemu-arm64 Anders Roxell
2018-12-13 12:29 ` [RFC PATCH 1/3] config: provide a fragment to enable gdb for qemu Anders Roxell
2018-12-13 12:40 ` Mark Brown
2018-12-18 8:45 ` Anders Roxell
2018-12-18 9:07 ` Arnd Bergmann
2018-12-18 13:29 ` Mark Brown
2018-12-13 12:29 ` [RFC PATCH 2/3] lib/ubsan: default UBSAN_ALIGNMENT to not set Anders Roxell
2018-12-13 12:29 ` [RFC PATCH 3/3] arm64: add a new config option KTEST_RUNNABLE Anders Roxell
2018-12-13 15:18 ` Mark Brown
2019-01-07 14:39 ` Mark Rutland
2019-01-07 14:43 ` Mark Rutland
2019-01-07 17:55 ` Mark Brown
2019-01-07 17:59 ` Mark Rutland [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190107175911.GA11863@lakrids.cambridge.arm.com \
--to=mark.rutland@arm.com \
--cc=akpm@linux-foundation.org \
--cc=anders.roxell@linaro.org \
--cc=arnd@arndb.de \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--cc=will.deacon@arm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®