From: Gylstorff Quirin <quirin.gylstorff@siemens.com>
To: Jan Kiszka <jan.kiszka@siemens.com>, cip-dev@lists.cip-project.org
Subject: Re: [isar-cip-core][PATCH 0/2] kas update and menu support
Date: Tue, 26 Oct 2021 10:21:05 +0200 [thread overview]
Message-ID: <149e6d13-9472-8a5a-ca37-b16416a9fd6f@siemens.com> (raw)
In-Reply-To: <cover.1634924446.git.jan.kiszka@siemens.com>
Hi,
On 10/22/21 7:40 PM, Jan Kiszka wrote:
> 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.
>
> Quirin, please have a look if I modeled the dependencies for secure boot
> and SWUpdate correctly, exposed reasonable combinations and didn't
> forget something useful.
I check it and all option are there.
Quirin
>
> @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 (2):
> Update to kas 2.6
> Add kconfig menu
>
> .gitlab-ci.yml | 2 +-
> Kconfig | 146 +++++++++++++++++++++++++++
> README.md | 39 ++++---
> 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 +-
> 7 files changed, 177 insertions(+), 22 deletions(-)
> create mode 100644 Kconfig
>
next prev parent reply other threads:[~2021-10-26 8:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-22 17:40 [isar-cip-core][PATCH 0/2] kas update and menu support Jan Kiszka
2021-10-22 17:40 ` [isar-cip-core][PATCH 1/2] Update to kas 2.6 Jan Kiszka
2021-10-22 17:40 ` [isar-cip-core][PATCH 2/2] Add kconfig menu Jan Kiszka
2021-10-26 8:21 ` Gylstorff Quirin [this message]
2021-10-28 6:13 ` [isar-cip-core][PATCH 0/2] kas update and menu support Jan Kiszka
2021-11-09 13:04 ` [cip-dev] " Venkata.Pyla
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=149e6d13-9472-8a5a-ca37-b16416a9fd6f@siemens.com \
--to=quirin.gylstorff@siemens.com \
--cc=cip-dev@lists.cip-project.org \
--cc=jan.kiszka@siemens.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