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)
1 file changed
tree: 100e7431e2b122730c86d0bfc22140c9c39c2c21
  1. conf/
  2. dynamic-layers/
  3. meta-nuvoton-npcm8xx/
  4. recipes-bsp/
  5. recipes-connectivity/
  6. recipes-core/
  7. recipes-devtools/
  8. recipes-extended/
  9. recipes-google/
  10. recipes-kernel/
  11. recipes-phosphor/
  12. recipes-support/
  13. LICENSE
  14. README.md
README.md

meta-gbmc-staging

This repository contains additions to the openbmc/meta-google layer that are not yet ready for OpenBMC inclusion.

How to use this layer

  1. Clone openbmc/openbmc from GitHub.
  2. Clone this layer from GitHub into a subdirectory of openbmc.