From: "Mark Brown" <broonie@kernel.org>
To: kernelci@groups.io, clabbe@baylibre.com
Subject: Re: Add more arches to kernelci via QEMU devices (part2)
Date: Fri, 21 Jun 2019 12:28:16 +0100 [thread overview]
Message-ID: <20190621112816.GF5316@sirena.org.uk> (raw)
In-Reply-To: <CA+j61XPeb0rjEO_=e8-bhdm9c79Wm=az_o=o9TtNwMhROSKB4w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 583 bytes --]
On Fri, Jun 21, 2019 at 11:24:16AM +0200, Corentin Labbe wrote:
> 4) defconfig hacks
> Some qemu machines can only be booted if defconfig are hacked.
> Examples are
> - need to disable cryptohw in exynos/cubieboard
> - need to disable some CONFIG for omap1
> Does kernelci want to build extra defconfig+hacks ?
These seem like bugs, we probably shouldn't be using those emulations if
they don't work - it's not like it's the only way to get coverage of 32
bit Arm or anything.
One question if we're going to start covering new architectures is where
are the builders coming from?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-06-21 11:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-21 9:24 Add more arches to kernelci via QEMU devices (part2) Corentin Labbe
2019-06-21 11:28 ` Mark Brown [this message]
2019-06-26 16:35 ` Kevin Hilman
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=20190621112816.GF5316@sirena.org.uk \
--to=broonie@kernel.org \
--cc=clabbe@baylibre.com \
--cc=kernelci@groups.io \
/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