From: Jan Kiszka <jan.kiszka@siemens.com>
To: "[ext] Henning Schild" <henning.schild@siemens.com>,
"Maxim Yu. Osipov" <mosipov@ilbers.de>
Cc: isar-users@googlegroups.com
Subject: Re: [PATCH v2] conf: Add support for new debian distro "buster"
Date: Thu, 16 Aug 2018 10:56:55 +0200 [thread overview]
Message-ID: <86a5ee5a-b686-860d-2436-55233a7ed3a3@siemens.com> (raw)
In-Reply-To: <20180816104813.02789fa3@md1pvb1c.ad001.siemens.net>
On 2018-08-16 10:48, [ext] Henning Schild wrote:
> Am Wed, 15 Aug 2018 04:26:09 +0200
> schrieb "Maxim Yu. Osipov" <mosipov@ilbers.de>:
>
>> From: Henning Schild <henning.schild@siemens.com>
>>
>> Let us already include support for "buster" in Isar, to prove that we
>> can build images and to find issues before it is declared stable.
>>
>> Note:
>> arm64-buster support is excluded so far as build on debian stretch
>> system hangs with error "qemu: unsupported syscall 277"
>
> How about still adding the configs but not building in CI? And does the
> error come from a stretch or a jessie qemu, maybe the newer one will
> work just fine?
kas-project/kas-isar:next is now on stretch - could be checked easily.
Jan
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2018-08-16 8:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-15 2:26 Maxim Yu. Osipov
2018-08-16 8:48 ` Henning Schild
2018-08-16 8:56 ` Jan Kiszka [this message]
2018-08-16 9:04 ` Maxim Yu. Osipov
2018-08-16 9:04 ` Henning Schild
2018-08-16 11:57 ` Maxim Yu. Osipov
2018-08-16 14:49 ` Henning Schild
2018-08-16 14:51 ` Jan Kiszka
2018-08-16 15:03 ` Henning Schild
2018-08-16 15:04 ` Jan Kiszka
2018-08-16 15:10 ` Henning Schild
2018-08-16 15:14 ` Jan Kiszka
2018-08-16 16:20 ` Henning Schild
2018-08-16 16:25 ` Jan Kiszka
2018-08-16 15:10 ` Maxim Yu. Osipov
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=86a5ee5a-b686-860d-2436-55233a7ed3a3@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=henning.schild@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=mosipov@ilbers.de \
/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