public inbox for cip-dev@lists.cip-project.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: cip-dev@lists.cip-project.org
Subject: [isar-cip-core][PATCH v2 0/3] kas update, menu support, Isar update
Date: Tue,  2 Nov 2021 21:18:30 +0100	[thread overview]
Message-ID: <cover.1635884313.git.jan.kiszka@siemens.com> (raw)

Changes in v2:
 - move to kas 2.6.2 bug-fix release
 - make security image depend on buster (apparently broken for other
   releases)
 - add Isar update

With kas 2.6 being released, this now allows to adopt the new "menu"
feature and make the various image flavors and options more accessible.

@all: Please play a bit with the options and check if you find anything
that does not work (crowd-sourced randconfig...).

Thanks,
Jan

Jan Kiszka (3):
  Update to kas 2.6.2
  Add kconfig menu
  Update Isar revision

 .gitignore                           |   1 +
 .gitlab-ci.yml                       |   2 +-
 Kconfig                              | 147 +++++++++++++++++++++++++++
 README.md                            |  39 ++++---
 kas-cip.yml                          |   2 +-
 kas/opt/ebg-secure-boot-base.yml     |   2 +-
 kas/opt/ebg-secure-boot-snakeoil.yml |   2 +-
 kas/opt/ebg-snakeoil-swu.yml         |   4 +-
 kas/opt/ebg-swu.yml                  |   4 +-
 9 files changed, 180 insertions(+), 23 deletions(-)
 create mode 100644 Kconfig

-- 
2.31.1



             reply	other threads:[~2021-11-02 20:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-02 20:18 Jan Kiszka [this message]
2021-11-02 20:18 ` [isar-cip-core][PATCH v2 1/3] Update to kas 2.6.2 Jan Kiszka
2021-11-02 20:18 ` [isar-cip-core][PATCH v2 2/3] Add kconfig menu Jan Kiszka
2021-11-02 20:18 ` [isar-cip-core][PATCH v2 3/3] Update Isar revision 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.1635884313.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