Re: [RESEND PATCH V2 0/5] Fixups to work with crash tool

[Conor.Dooley]

On 26/07/2022 08:54, tianxianting wrote:
> 
> 在 2022/7/26 上午1:13, Conor.Dooley@xxxxxxxxxxxxx 写道:
>> That said, this does not apply to riscv/for-next:
>> b4 shazam 20220725014539.1037627-1-xianting.tian@xxxxxxxxxxxxxxxxx
>> Grabbing thread from lore.kernel.org/all/20220725014539.1037627-1-xianting.tian%40linux.alibaba.com/t.mbox.gz
>> Checking for newer revisions on https://lore.kernel.org/all/
>> Analyzing 6 messages in the thread
>> Checking attestation on all messages, may take a moment...
>> ---
>>    [PATCH v2 1/5] RISC-V: use __smp_processor_id() instead of smp_processor_id()
>>    [PATCH v2 2/5] RISC-V: Add arch_crash_save_vmcoreinfo support
>>    [PATCH v2 3/5] riscv: Add modules to virtual kernel memory layout dump
>>    [PATCH v2 4/5] RISC-V: Fixup getting correct current pc
>>    [PATCH v2 5/5] riscv: crash_core: Export kernel vm layout, phys_ram_base
>> ---
>> Total patches: 5
>> ---
>> Applying: RISC-V: use __smp_processor_id() instead of smp_processor_id()
>> Applying: RISC-V: Add arch_crash_save_vmcoreinfo support
>> Patch failed at 0002 RISC-V: Add arch_crash_save_vmcoreinfo support
> 
> patch 2 apply is OK for me, I don't know why you failed :(
> Do you have more detals for this?
> 

What did you apply it to? It does not apply for me to riscv/for-next:
https://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git/log/?h=for-next

Thanks,
Conor.