From: Jan Kiszka <jan.kiszka@siemens.com>
To: cip-dev@lists.cip-project.org
Subject: [isar-cip-core][PATCH 0/2] Isar update
Date: Tue, 17 Oct 2023 07:59:13 +0200 [thread overview]
Message-ID: <cover.1697522355.git.jan.kiszka@siemens.com> (raw)
Late Isar update to bring in its fixes and allow us to model the
dosfstools build more cleanly.
Jan
Jan Kiszka (2):
Update Isar revision
dosfstools: Use -native suffix to select the right architecture
conf/distro/cip-core-common.inc | 4 ++--
kas-cip.yml | 2 +-
recipes-bsp/edk2/edk2-standalonemm-rpmb_202305.bb | 3 +++
recipes-devtools/dosfstools/dosfstools_latest.bb | 3 ---
4 files changed, 6 insertions(+), 6 deletions(-)
--
2.35.3
next reply other threads:[~2023-10-17 5:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-17 5:59 Jan Kiszka [this message]
2023-10-17 5:59 ` [isar-cip-core][PATCH 1/2] Update Isar revision Jan Kiszka
2023-10-17 5:59 ` [isar-cip-core][PATCH 2/2] dosfstools: Use -native suffix to select the right architecture Jan Kiszka
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=cover.1697522355.git.jan.kiszka@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=cip-dev@lists.cip-project.org \
/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