From 367ca6e16b3989bf132b5b4081ec94d6cf1806d2 Mon Sep 17 00:00:00 2001
From: Marc Hartmayer <marc@linux.ibm.com>
Date: Thu, 18 Jun 2026 10:28:04 +0200
Subject: [PATCH] pvimg: Add comment why cck and not cck-available is required
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Add a comment to the code to explain why cck and not cck-available is
required.

Reviewed-by: Steffen Eiden <seiden@linux.ibm.com>
Signed-off-by: Marc Hartmayer <marc@linux.ibm.com>
Signed-off-by: Jan Höppner <hoeppner@linux.ibm.com>
---
 rust/pvimg/src/cli.rs | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/rust/pvimg/src/cli.rs b/rust/pvimg/src/cli.rs
index 25ac0b87..652e500a 100644
--- a/rust/pvimg/src/cli.rs
+++ b/rust/pvimg/src/cli.rs
@@ -154,6 +154,9 @@ pub struct CreateBootImageLegacyFlags {
     /// Add-secret requests must provide an extension secret that matches the
     /// CCK-derived extension secret. This option requires the '--cck'
     /// option.
+    // Note: We intentionally require 'cck' (not 'cck-available') because
+    // enable-cck-extension-secret cannot be used together with
+    // --enable-cck-update.
     #[arg(long, action = clap::ArgAction::SetTrue, requires="cck", group="header-flags")]
     pub enable_cck_extension_secret: Option<bool>,