From: "Jan Kiszka" <jan.kiszka@siemens.com>
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] [isar-cip-core][PATCH 0/3] Some updates
Date: Mon, 30 Nov 2020 20:32:13 +0100 [thread overview]
Message-ID: <cover.1606764736.git.jan.kiszka@siemens.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1903 bytes --]
The last patch has to wait until [1] is rolled out to our CI
infrastructure.
Jan
[1] https://gitlab.com/cip-project/cip-testing/gitlab-cloud-ci/-/commit/1cd85bec680587b9410c56cdfebc3a4d6ba1bd8b
Jan Kiszka (3):
README: Add some community resources
Update Isar revision
Update to kas 2.3.3
.gitignore | 3 +-
.gitlab-ci.yml | 2 +-
README.md | 29 ++-
conf/distro/cip-core-buster.conf | 2 +
conf/distro/cip-core-stretch.conf | 2 +
doc/README.secureboot.md | 4 +-
doc/README_iwg20m.md | 11 +-
.../0001-u-boot-add-libubootenv.patch | 168 ------------------
kas-cip.yml | 9 +-
kas/board/bbb.yml | 2 +-
kas/board/hihope-rzg2m.yml | 2 +-
kas/board/iwg20m.yml | 2 +-
kas/board/qemu-amd64.yml | 2 +-
kas/board/simatic-ipc227e.yml | 2 +-
kas/opt/4.4.yml | 2 +-
kas/opt/ebg-secure-boot-base.yml | 2 +-
kas/opt/ebg-secure-boot-snakeoil.yml | 2 +-
kas/opt/ebg-swu.yml | 2 +-
kas/opt/qemu-swupdate.yml | 2 +-
kas/opt/rt.yml | 2 +-
kas/opt/security.yml | 2 +-
kas/opt/stretch.yml | 2 +-
kas/opt/targz-img.yml | 2 +-
kas/opt/test.yml | 2 +-
.../wic/plugins/source/efibootguard-boot.py | 2 +-
.../wic/plugins/source/efibootguard-efi.py | 2 +-
26 files changed, 57 insertions(+), 207 deletions(-)
delete mode 100644 isar-patches/0001-u-boot-add-libubootenv.patch
--
2.26.2
[-- Attachment #2: Type: text/plain, Size: 420 bytes --]
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#5906): https://lists.cip-project.org/g/cip-dev/message/5906
Mute This Topic: https://lists.cip-project.org/mt/78616510/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-
next reply other threads:[~2020-11-30 19:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-30 19:32 Jan Kiszka [this message]
2020-11-30 19:32 ` [cip-dev] [isar-cip-core][PATCH 1/3] README: Add some community resources Jan Kiszka
2020-11-30 19:32 ` [cip-dev] [isar-cip-core][PATCH 2/3] Update Isar revision Jan Kiszka
2020-11-30 19:32 ` [cip-dev] [isar-cip-core][PATCH 3/3] Update to kas 2.3.3 Jan Kiszka
2020-12-01 16:35 ` [cip-dev] [isar-cip-core][PATCH 0/3] Some updates 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.1606764736.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.