From: Baurzhan Ismagulov <ibr@radix50.net>
To: isar-users@googlegroups.com
Subject: Re: [PATCH v2 0/9] Add mipsel architecture and QEMU machine
Date: Wed, 12 Jun 2019 19:23:13 +0200 [thread overview]
Message-ID: <20190612172312.GK3977@yssyq.m.ilbers.de> (raw)
In-Reply-To: <1560257426-225-1-git-send-email-Cedric_Hombourger@mentor.com>
On Tue, Jun 11, 2019 at 02:50:17PM +0200, Cedric Hombourger wrote:
> This patch series adds the mipsel architecture and a QEMU machine to Isar to
> support legacy projects wanting to migrate to Debian (the mipsel architecture
> and Malta reference board are supported with both stretch and buster). The
> last patch is optional but desirable: it would add the qemumipsel-stretch
> configuration to the ci_build chain.
Looks good to me. ci_build is always welcome. vm_smoke_test and
testsuite/start_vm.py would be great, too.
Applied to next, thanks.
With kind regards,
Baurzhan.
next prev parent reply other threads:[~2019-06-12 17:23 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-11 5:38 [PATCH 0/7] " Cedric Hombourger
2019-06-11 5:38 ` [PATCH 1/7] image.bbclass: introduce KERNEL_FILE (defaults to vmlinuz) Cedric Hombourger
2019-06-11 5:38 ` [PATCH 2/7] start_vm: append kernel arguments specified in QEMU_KARGS Cedric Hombourger
2019-06-11 5:38 ` [PATCH 3/7] recipes-devtools/*-apt: add support for the mipsel architecture Cedric Hombourger
2019-06-11 5:38 ` [PATCH 4/7] recipes-kernel/linux: " Cedric Hombourger
2019-06-11 5:38 ` [PATCH 5/7] start_vm: add mipsel to the list of supported architectures Cedric Hombourger
2019-06-11 5:38 ` [PATCH 6/7] meta-isar: add the qemumipsel machine Cedric Hombourger
2019-06-11 5:38 ` [PATCH 7/7] ci_build: add qemumipsel-stretch to build targets Cedric Hombourger
2019-06-11 8:42 ` Henning Schild
2019-06-11 8:44 ` Hombourger, Cedric
2019-06-11 11:07 ` Henning Schild
2019-06-11 12:50 ` [PATCH v2 0/9] Add mipsel architecture and QEMU machine Cedric Hombourger
2019-06-11 12:50 ` [PATCH v2 1/9] image.bbclass: introduce KERNEL_FILE (defaults to vmlinuz) Cedric Hombourger
2019-06-11 12:50 ` [PATCH v2 2/9] start_vm: append kernel arguments specified in QEMU_KARGS Cedric Hombourger
2019-06-11 12:50 ` [PATCH v2 3/9] recipes-devtools/*-apt: add support for the mipsel architecture Cedric Hombourger
2019-06-11 12:50 ` [PATCH v2 4/9] recipes-kernel/linux: " Cedric Hombourger
2019-06-11 12:56 ` [PATCH v2 5/9] start_vm: add mipsel to the list of supported architectures Cedric Hombourger
2019-06-11 12:56 ` [PATCH v2 6/9] meta-isar: add the qemumipsel machine Cedric Hombourger
2019-06-11 12:56 ` [PATCH v2 7/9] ci_build: add qemumipsel-stretch to build targets Cedric Hombourger
2019-06-11 12:56 ` [PATCH v2 8/9] meta-isar: add qemumipsel-buster configuration Cedric Hombourger
2019-06-11 12:56 ` [PATCH v2 9/9] ci_build: add qemumipsel-buster configuration to build targets Cedric Hombourger
2019-06-11 12:59 ` [PATCH v2 0/9] Add mipsel architecture and QEMU machine chombourger
2019-06-12 9:30 ` Claudius Heine
2019-06-12 9:44 ` chombourger
2019-06-12 11:21 ` Baurzhan Ismagulov
2019-06-12 11:27 ` Claudius Heine
2019-06-12 17:23 ` Baurzhan Ismagulov [this message]
2019-06-12 17:43 ` chombourger
2019-06-11 7:36 ` [PATCH 0/7] " Claudius Heine
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=20190612172312.GK3977@yssyq.m.ilbers.de \
--to=ibr@radix50.net \
--cc=isar-users@googlegroups.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