From: "Mark Brown" <broonie@kernel.org>
To: Will Deacon <will@kernel.org>
Cc: Veronika Kabatova <vkabatov@redhat.com>,
kernelci@groups.io, Catalin Marinas <catalin.marinas@arm.com>,
tkjos@google.com
Subject: Re: Branch for kernelci
Date: Thu, 17 Oct 2019 17:11:37 +0100 [thread overview]
Message-ID: <20191017161137.GG4976@sirena.co.uk> (raw)
In-Reply-To: <20191017160242.qgp5y56gnbxnmkaa@willie-the-truck>
[-- Attachment #1: Type: text/plain, Size: 620 bytes --]
On Thu, Oct 17, 2019 at 05:02:43PM +0100, Will Deacon wrote:
> Curious: why 'olddefconfig' instead of 'defconfig'? Are there some options
> required by CKI that aren't present in defconfig?
In general anything that's doing runtime tests will need some extra
config options to get the functionality they're trying to test enabled,
for example for kselftests there's fragments in tree as
tools/testing/selftests/*/config (a lot though not all of those tend to
end up in defconfigs but other testsuites end up adding more). This was
why Anders was looking at making allmodconfig bootable, it'd reduce the
need for this.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-10-17 16:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20191015202114.GA120152@google.com>
2019-10-15 20:52 ` Branch for kernelci Todd Kjos
2019-10-16 9:56 ` Mark Brown
2019-10-16 12:38 ` Catalin Marinas
2019-10-16 12:54 ` Mark Brown
2019-10-16 16:46 ` Will Deacon
2019-10-16 17:28 ` Veronika Kabatova
2019-10-16 23:50 ` Will Deacon
2019-10-17 11:31 ` Veronika Kabatova
2019-10-17 16:02 ` Will Deacon
2019-10-17 16:11 ` Mark Brown [this message]
2019-10-17 17:01 ` Veronika Kabatova
2019-10-22 19:53 ` Guillaume Tucker
2019-10-23 16:42 ` Will Deacon
2019-10-23 18:16 ` Guillaume Tucker
2019-10-25 16:01 ` Will Deacon
2019-10-28 21:10 ` Guillaume Tucker
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=20191017161137.GG4976@sirena.co.uk \
--to=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=kernelci@groups.io \
--cc=tkjos@google.com \
--cc=vkabatov@redhat.com \
--cc=will@kernel.org \
/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