public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Anton Mikanovich <amikan@ilbers.de>,
	isar-users <isar-users@googlegroups.com>
Cc: Nishanth Menon <nm@ti.com>, Baurzhan Ismagulov <ibr@ilbers.de>
Subject: Re: [PATCH 0/9] Add support for BeaglePlay
Date: Mon, 8 Jan 2024 16:07:16 +0100	[thread overview]
Message-ID: <7bd5fcc6-340b-4525-b54c-dc6ed5463155@siemens.com> (raw)
In-Reply-To: <c73c6db7-4cbe-452f-b5a7-bb593026b16f@ilbers.de>

On 08.01.24 14:53, Anton Mikanovich wrote:
> 08/01/2024 14:18, Jan Kiszka wrote:
>> Sure - but where exactly? CrossTest?
>>
>> Jan
>>
> We don't have full-cross test cases jet, but this rebuild is already
> scheduled.
> So currently the only option is: test_nocross()
> And when we will rebuild full CI into two major test cases (full-cross +
> full+nocross) it will go to cross.

I just don't want another no-cross kernel build added to the CI test -
wasted resources. It seem hikey is already in the same boat, but we
should not do ANY non-cross kernel build in CI in fact.

Jan

-- 
Siemens AG, Technology
Linux Expert Center


      reply	other threads:[~2024-01-08 15:07 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-07 12:54 Jan Kiszka
2024-01-07 12:54 ` [PATCH 1/9] meta-isar: linux-mainline: Update to 6.6.10 Jan Kiszka
2024-01-07 12:54 ` [PATCH 2/9] optee-os: Switch default binary to tee-raw.bin Jan Kiszka
2024-01-07 12:54 ` [PATCH 3/9] u-boot-custom: Allow to set BL31 and TEE from recipes Jan Kiszka
2024-01-07 12:54 ` [PATCH 4/9] u-boot-custom: Allow to define different installation binaries Jan Kiszka
2024-01-07 12:54 ` [PATCH 5/9] beagleplay: Add TF-A recipe Jan Kiszka
2024-01-08 12:49   ` Florian Bezdeka
2024-01-07 12:54 ` [PATCH 6/9] beagleplay: Add OP-TEE recipe Jan Kiszka
2024-01-07 12:54 ` [PATCH 7/9] beagleplay: Add U-Boot recipe Jan Kiszka
2024-01-08 13:17   ` Florian Bezdeka
2024-01-08 13:19     ` Jan Kiszka
2024-01-07 12:54 ` [PATCH 8/9] Add support for the BeaglePlay board Jan Kiszka
2024-01-07 16:40   ` Jan Kiszka
2024-01-07 12:54 ` [PATCH 9/9] expand-on-first-boot: Preserve MBR on expansion of GPT disks Jan Kiszka
2024-01-08  8:51 ` [PATCH 0/9] Add support for BeaglePlay Anton Mikanovich
2024-01-08 12:18   ` Jan Kiszka
2024-01-08 13:53     ` Anton Mikanovich
2024-01-08 15:07       ` Jan Kiszka [this message]

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=7bd5fcc6-340b-4525-b54c-dc6ed5463155@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=amikan@ilbers.de \
    --cc=ibr@ilbers.de \
    --cc=isar-users@googlegroups.com \
    --cc=nm@ti.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