commit 104c81ce11e20d2286a9219fb2ff6e5f1465b7ce
author Yuxiao Zhang <yuxiaozhang@google.com> Mon Nov 27 14:47:13 2023 -0800
committer Yuxiao Zhang <yuxiaozhang@google.com> Tue Nov 28 00:23:49 2023 +0000
tree 100e7431e2b122730c86d0bfc22140c9c39c2c21
parent a2e98c5c04f6ff40d16468fefdd51187f26eabc4

kdump: using move instead of copy

We can safely remove the one in ramFS after transfering to emmc, no need
to preserve it.

Google-Bug-Id:313504742
Change-Id: I75eeb363dd391693c49d4b52f557962e81f010b4
Signed-off-by: Yuxiao Zhang <yuxiaozhang@google.com>
(cherry picked from commit 81e90ff641a725832b0644c70d002bb0daccdb97)

recipes-google/emmc/emmc-kdump/emmc_kdump.sh

diff --git a/recipes-google/emmc/emmc-kdump/emmc_kdump.sh b/recipes-google/emmc/emmc-kdump/emmc_kdump.sh
index bd95977..6aad8bb 100644
--- a/recipes-google/emmc/emmc-kdump/emmc_kdump.sh
+++ b/recipes-google/emmc/emmc-kdump/emmc_kdump.sh
@@ -24,4 +24,4 @@
 fi
 
 # At most 1 kdump in ram at any time
-cp /run/log/kdump/* . || exit 0
+mv /run/log/kdump/* . || exit 0