From: Claudius Heine <claudius.heine.ext@siemens.com>
To: chombourger@gmail.com, isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH v2 0/9] Add mipsel architecture and QEMU machine
Date: Wed, 12 Jun 2019 11:30:16 +0200 [thread overview]
Message-ID: <bbfa7909-236b-07f5-78fe-afde1cd10c10@siemens.com> (raw)
In-Reply-To: <c0f2bb11-9154-46da-8651-4a251f3c5d3b@googlegroups.com>
Hi Cedric,
On 11/06/2019 14.59, chombourger@gmail.com wrote:
> I hope the patch series reached the mailing list OK (especially for git am
> user) as my company e-mail server decided that 9 patches was too much :)
> it stopped after patch #4 with: 4.4.2 Message submission rate for this
> client has exceeded the configured limit
>
> I did another git send-email for patches 5-9 and use the ID of patch #4 as
> reference
I think #8 is still missing.
Claudius
>
> Cedric
>
> On Tuesday, June 11, 2019 at 2:50:43 PM UTC+2, 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.
>>
>> ChangeLog:
>> * v2: add qemumipsel-buster configuration
>> * v1: initial submission (targeting qemumipsel-stretch)
>>
>> Cedric Hombourger (9):
>> image.bbclass: introduce KERNEL_FILE (defaults to vmlinuz)
>> start_vm: append kernel arguments specified in QEMU_KARGS
>> recipes-devtools/*-apt: add support for the mipsel architecture
>> recipes-kernel/linux: add support for the mipsel architecture
>> start_vm: add mipsel to the list of supported architectures
>> meta-isar: add the qemumipsel machine
>> ci_build: add qemumipsel-stretch to build targets
>> meta-isar: add qemumipsel-buster configuration
>> ci_build: add qemumipsel-buster configuration to build targets
>>
>> meta-isar/conf/local.conf.sample | 2 ++
>> meta-isar/conf/machine/qemumipsel.conf | 9 +++++++++
>> meta-isar/conf/multiconfig/qemumipsel-buster.conf | 17
>> +++++++++++++++++
>> meta-isar/conf/multiconfig/qemumipsel-stretch.conf | 17
>> +++++++++++++++++
>> meta/classes/image.bbclass | 5 +++--
>> meta/recipes-devtools/base-apt/files/distributions.in | 2 +-
>> meta/recipes-devtools/isar-apt/files/distributions.in | 2 +-
>> meta/recipes-kernel/linux/files/build-kernel.sh | 4 ++++
>> scripts/ci_build.sh | 2 ++
>> scripts/start_vm | 6 +++---
>> 10 files changed, 59 insertions(+), 7 deletions(-)
>> create mode 100644 meta-isar/conf/machine/qemumipsel.conf
>> create mode 100644 meta-isar/conf/multiconfig/qemumipsel-buster.conf
>> create mode 100644 meta-isar/conf/multiconfig/qemumipsel-stretch.conf
>>
>> --
>> 2.11.0
>>
>>
>
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-54 Fax: (+49)-8142-66989-80 Email: ch@denx.de
next prev parent reply other threads:[~2019-06-12 9:30 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 [this message]
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
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=bbfa7909-236b-07f5-78fe-afde1cd10c10@siemens.com \
--to=claudius.heine.ext@siemens.com \
--cc=chombourger@gmail.com \
--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