From 383cb622029a52dd1cb460144aa8e62ed0907d73 Mon Sep 17 00:00:00 2001
From: Philipp Rudo <prudo@redhat.com>
Date: Thu, 12 Jan 2023 16:31:03 +0100
Subject: [PATCH] mkfadumprd: drop unset globals from debug output

mkfadumprd doesn't call prepare_kdump_bootinfo from kdump-lib.sh. Thus
both KDUMP_KERNELVER and DEFAULT_INITRD are always empty. Simply remove
them from the debug print.

Signed-off-by: Philipp Rudo <prudo@redhat.com>
Reviewed-by: Coiby Xu <coxu@redhat.com>
---
 mkfadumprd | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 mode change 100644 => 100755 mkfadumprd

diff --git a/mkfadumprd b/mkfadumprd
old mode 100644
new mode 100755
index 2fc396c..719e150
--- a/mkfadumprd
+++ b/mkfadumprd
@@ -37,7 +37,7 @@ FADUMP_INITRD="$MKFADUMPRD_TMPDIR/fadump.img"
 ### First build an initramfs with dump capture capability
 # this file tells the initrd is fadump enabled
 touch "$MKFADUMPRD_TMPDIR/fadump.initramfs"
-ddebug "rebuild fadump initrd: $FADUMP_INITRD $DEFAULT_INITRD $KDUMP_KERNELVER"
+ddebug "rebuild fadump initrd: $FADUMP_INITRD"
 # Don't use squash for capture image or default image as it negatively impacts
 # compression ratio and increases the size of the initramfs image.
 # Don't compress the capture image as uncompressed image is needed immediately.