From: Matt Madison <matt@madison.systems>
To: openembedded-core@lists.openembedded.org
Cc: Alexander Kanavin <alex@linutronix.de>,
Khem Raj <raj.khem@gmail.com>,
Richard Purdie <richard.purdie@linuxfoundation.org>,
Matt Madison <matt@madison.systems>
Subject: [OE-core][PATCH v2 0/2] qemu.bbclass: drop OLDEST_KERNEL reference
Date: Thu, 16 Dec 2021 03:48:34 -0800 [thread overview]
Message-ID: <20211216114836.964835-1-matt@madison.systems> (raw)
This addresses an issue with allarch recipes that use meson, where
inheriting qemu.bbclass causes task signature changes when built with
MACHINEs with different architectures due to the reference to the
OLDEST_KERNEL variable for setting up qemu wrapper invocations.
V2:
* Backport Khem's qemu patch to set minimum kernel version for riscv32.
With this patch, qemu for all supported archs should have a built-in
oldest kernel setting, eliminating the need for putting it on the
command line.
Matt Madison (2):
qemu.bbclass: drop OLDEST_KERNEL reference
qemu: add patch to set minimum kernel version for riscv32
meta/classes/qemu.bbclass | 2 +-
meta/recipes-devtools/qemu/qemu.inc | 1 +
...s-minimum-kernel-version-for-riscv32.patch | 40 +++++++++++++++++++
3 files changed, 42 insertions(+), 1 deletion(-)
create mode 100644 meta/recipes-devtools/qemu/qemu/0001-riscv-Set-5.4-as-minimum-kernel-version-for-riscv32.patch
--
2.32.0
next reply other threads:[~2021-12-16 11:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-16 11:48 Matt Madison [this message]
2021-12-16 11:48 ` [OE-core][PATCH v2 1/2] qemu.bbclass: drop OLDEST_KERNEL reference Matt Madison
2021-12-30 8:51 ` Changqing Li
2021-12-30 11:06 ` Alexander Kanavin
2021-12-30 13:21 ` Richard Purdie
2021-12-31 0:50 ` Changqing Li
2021-12-16 11:48 ` [OE-core][PATCH v2 2/2] qemu: add patch to set minimum kernel version for riscv32 Matt Madison
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=20211216114836.964835-1-matt@madison.systems \
--to=matt@madison.systems \
--cc=alex@linutronix.de \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
--cc=richard.purdie@linuxfoundation.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