Re: [PATCH] Revert "riscv: kdump: fix crashkernel reserving problem on RISC-V"

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Apr 16, 2024 at 04:56:47PM +0800, Mingzheng Xing wrote:
> This reverts commit 1d6cd2146c2b58bc91266db1d5d6a5f9632e14c0 which has been
> merged into the mainline commit 39365395046f ("riscv: kdump: use generic
> interface to simplify crashkernel reservation"), but the latter's series of
> patches are not included in the 6.6 branch.
> 
> This will result in the loss of Crash kernel data in /proc/iomem, and kdump
> loading the kernel will also cause an error:
> 
> ```
> Memory for crashkernel is not reserved
> Please reserve memory by passing"crashkernel=Y@X" parameter to kernel
> Then try to loading kdump kernel
> ```
> 
> After revert this patch, verify that it works properly on QEMU riscv.
> 
> Link: https://lore.kernel.org/linux-riscv/ZSiQRDGLZk7lpakE@MiWiFi-R3L-srv
> Signed-off-by: Mingzheng Xing <xingmingzheng@xxxxxxxxxxx>
> ---

I do not understand, what branch is this for?  Why have you not cc:ed
any of the original developers here?  Why does Linus's tree not have the
same problem?  And the first sentence above does not make much sense as
a 6.6 change is merged into 6.7?

confused,

greg k-h




[Index of Archives]     [Linux Kernel]     [Kernel Development Newbies]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Hiking]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux