Re: [PATCH V4 0/5] RISC-V fixups to work with crash tool

[Xianting Tian <xianting.tian@linux.alibaba.com>]

在 2022/7/26 下午5:52, Conor.Dooley@microchip.com 写道:
> On 26/07/2022 10:37, Xianting Tian wrote:
>> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
> Ah I see you've already sent a v4.
>
>> Changes v1 -> v2:
>>    1, remove the patch "Add a fast call path of crash_kexec()" from this series
>>    of patches, as it already applied to riscv git.
>>    https://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git/commit/?h=for-next&id=3f1901110a89b0e2e13adb2ac8d1a7102879ea98
>>    2, add 'Reviewed-by' based on the comments of v1.
>> Changes v2 -> v3:
>>    use "riscv" instead of "riscv64" in patch 5 subject line.
>> Changes v3 -> v4:
>>    use "riscv" instead of "riscv64" in the summary of patch 5 subject line.
> There's no need to respin a series for the sake 3 characters in the cover
> letter (so sorry if you misunderstood me!)...
>
>> Xianting Tian (5):
>>     RISC-V: use __smp_processor_id() instead of smp_processor_id()
>>     RISC-V: Add arch_crash_save_vmcoreinfo support
>>     riscv: Add modules to virtual kernel memory layout dump
>>     RISC-V: Fixup getting correct current pc
>>     riscv: crash_core: Export kernel vm layout, phys_ram_base
> ...but it would've been good to align these to either "riscv:" or
> "RISC-V:" & not mix the two in a series. Don't do this right away,
> it is okay to wait for more significant changes before sending out
> a new version as this sort of thing could easily be changed when
> being applied.
Many thanks, I got it, waiting these patches to be applied:)
>
> Thanks,
> Conor.
>
>

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv