CIP-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Bezdeka <florian.bezdeka@siemens.com>
To: <jan.kiszka@siemens.com>, <cip-dev@lists.cip-project.org>
Subject: Re: [cip-dev] [isar-cip-core][PATCH 08/14] Kconfig: Do not offer swupdate or security options without a kernel
Date: Tue, 02 Dec 2025 10:55:59 +0100	[thread overview]
Message-ID: <DENN2WDIIV2G.1W0RTBCWK231A@siemens.com> (raw)
In-Reply-To: <6b42744057af96e3f1c00918aeed3c5ad2e9202b.1764667279.git.jan.kiszka@siemens.com>

On Tue Dec 2, 2025 at 10:21 AM CET, Jan Kiszka via lists.cip-project.org wrote:
> From: Jan Kiszka <jan.kiszka@siemens.com>
>
> Those variants only make sense for full images with a kernel.
>
> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
> ---
>  Kconfig | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Kconfig b/Kconfig
> index deb6044d..f8a93c2d 100644
> --- a/Kconfig
> +++ b/Kconfig
> @@ -258,7 +258,7 @@ config KAS_INCLUDE_TESTING
>  	string
>  	default "kas/opt/test.yml" if IMAGE_TESTING
>  
> -if !KERNEL_4_4 && !KERNEL_4_19
> +if !KERNEL_4_4 && !KERNEL_4_19 &&!NO_KERNEL
                                   ^^^
Missing space.

>  
>  config IMAGE_SECURITY
>  	bool "Security extensions"



  reply	other threads:[~2025-12-02  9:56 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-02  9:21 [isar-cip-core][PATCH 00/14] CI changes to move testing to trixie Jan Kiszka
2025-12-02  9:21 ` [isar-cip-core][PATCH 01/14] tests: Avoid hard-coding distribution in M-COM test Jan Kiszka
2025-12-02  9:21 ` [isar-cip-core][PATCH 02/14] ci: Prepare for running non-bookworm secure boot tests Jan Kiszka
2025-12-02  9:44   ` [cip-dev] " Florian Bezdeka
2025-12-02  9:48     ` Jan Kiszka
2025-12-02  9:21 ` [isar-cip-core][PATCH 03/14] ci: Select qemu-amd64 OVMF according to target release Jan Kiszka
2025-12-02  9:21 ` [isar-cip-core][PATCH 04/14] ci: Raise qemu x86 CPU model Jan Kiszka
2025-12-02  9:21 ` [isar-cip-core][PATCH 05/14] qemu-amd64: Raise boot watchdog timeout to 120 seconds Jan Kiszka
2025-12-02  9:21 ` [isar-cip-core][PATCH 06/14] ci: Inject image version into common cip-core-image.inc Jan Kiszka
2025-12-02  9:21 ` [isar-cip-core][PATCH 07/14] ci: Clean up no-kernel deployment Jan Kiszka
2025-12-02  9:21 ` [isar-cip-core][PATCH 08/14] Kconfig: Do not offer swupdate or security options without a kernel Jan Kiszka
2025-12-02  9:55   ` Florian Bezdeka [this message]
2025-12-02 10:02     ` [cip-dev] " Jan Kiszka
2025-12-02  9:21 ` [isar-cip-core][PATCH 09/14] kas: Auto-enable targz format for kernelci images Jan Kiszka
2025-12-02  9:21 ` [isar-cip-core][PATCH 10/14] ci: Combine targz with no_kernel option Jan Kiszka
2025-12-02  9:21 ` [isar-cip-core][PATCH 11/14] ci: Make deployment opt-in Jan Kiszka
2025-12-02  9:21 ` [isar-cip-core][PATCH 12/14] ci: submit_lava.sh: Reduce number of sed calls Jan Kiszka
2025-12-02  9:21 ` [isar-cip-core][PATCH 13/14] ci: Build and deploy kernel-panic update artifact Jan Kiszka
2025-12-02  9:21 ` [isar-cip-core][PATCH 14/14] ci: Switch to trixie based builds and tests 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=DENN2WDIIV2G.1W0RTBCWK231A@siemens.com \
    --to=florian.bezdeka@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