From: Uladzimir Bely <ubely@ilbers.de>
To: Anton Mikanovich <amikan@ilbers.de>, isar-users@googlegroups.com
Subject: Re: [PATCH] meta-isar: Declare compatible machines
Date: Thu, 24 Aug 2023 18:18:30 +0300 [thread overview]
Message-ID: <8c2457fd21fd30a6a6582c71dc84e0792e7b3f14.camel@ilbers.de> (raw)
In-Reply-To: <20230817141524.1808562-1-amikan@ilbers.de>
On Thu, 2023-08-17 at 17:15 +0300, Anton Mikanovich wrote:
> Declare COMPATIBLE_MACHINE values for all machine-specific recipes.
>
> Signed-off-by: Anton Mikanovich <amikan@ilbers.de>
> ---
> meta-isar/recipes-bsp/bootconfig-rpi/bootconfig-rpi.bb | 2
> ++
> .../jh7110-u-boot-spl-image/jh7110-u-boot-spl-image_0.1.bb | 2
> ++
> .../jh7110-u-boot-spl-tool/jh7110-u-boot-spl-tool_0.1.bb | 2
> ++
> meta-isar/recipes-bsp/opensbi/opensbi-sifive-fu540_1.1.bb | 2
> ++
> .../opensbi/opensbi-starfive-visionfive2_1.2+20230310.bb | 2
> ++
> .../recipes-bsp/optee-client/optee-client-stm32mp15x_3.21.0.bb | 2
> ++
> .../optee-examples/optee-examples-stm32mp15x_3.21.0.bb | 2
> ++
> .../optee-ftpm/optee-ftpm-stm32mp15x_0~230316+git.bb | 2
> ++
> meta-isar/recipes-bsp/optee-os/optee-os-stm32mp15x_3.21.0.inc | 2
> ++
> .../trusted-firmware-a/trusted-firmware-a-stm32mp15x_2.4.bb | 2
> ++
> meta-isar/recipes-bsp/u-boot/u-boot-de0-nano-soc_2020.10.bb | 2
> ++
> .../u-boot-starfive-visionfive2_2022.01-rc4+VF2-2.11.5.bb | 2
> ++
> meta-isar/recipes-bsp/u-boot/u-boot-stm32mp15x_2020.10.bb | 2
> ++
> .../visionfive2-u-boot-firmware/visionfive2-u-boot-firmware.bb | 2
> ++
> meta-isar/recipes-kernel/linux/linux-phy_5.10.76-phy4.bb | 2
> ++
> .../recipes-kernel/linux/linux-starfive_5.15-visionfive2.bb | 2
> ++
> 16 files changed, 32 insertions(+)
Applied to next.
prev parent reply other threads:[~2023-08-24 15:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-17 14:15 Anton Mikanovich
2023-08-17 14:17 ` Anton Mikanovich
2023-08-17 14:24 ` Jan Kiszka
2023-08-17 14:33 ` Anton Mikanovich
2023-08-24 15:18 ` Uladzimir Bely [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=8c2457fd21fd30a6a6582c71dc84e0792e7b3f14.camel@ilbers.de \
--to=ubely@ilbers.de \
--cc=amikan@ilbers.de \
--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