Re: [PATCH -next v8 0/2] support allocating crashkernel above 4G explicitly on riscv

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

To: Chen Jiahao <chenjiahao16@xxxxxxxxxx>
Subject: Re: [PATCH -next v8 0/2] support allocating crashkernel above 4G explicitly on riscv
From: Conor Dooley <conor@xxxxxxxxxx>
Date: Tue, 25 Jul 2023 22:48:54 +0100
Cc: linux-kernel@xxxxxxxxxxxxxxx, linux-riscv@xxxxxxxxxxxxxxxxxxx, kexec@xxxxxxxxxxxxxxxxxxx, linux-doc@xxxxxxxxxxxxxxx, paul.walmsley@xxxxxxxxxx, palmer@xxxxxxxxxxx, conor.dooley@xxxxxxxxxxxxx, guoren@xxxxxxxxxx, heiko@xxxxxxxxx, bjorn@xxxxxxxxxxxx, alex@xxxxxxxx, akpm@xxxxxxxxxxxxxxxxxxxx, atishp@xxxxxxxxxxxx, bhe@xxxxxxxxxx, thunder.leizhen@xxxxxxxxxx, horms@xxxxxxxxxx
In-reply-to: <20230725214413.2488159-1-chenjiahao16@huawei.com>
References: <20230725214413.2488159-1-chenjiahao16@huawei.com>

Hey,

Your $subject says -next, but the patch failed to apply to
riscv/for-next. What was the base for this patchset?

Thanks,
Conor.

Attachment: signature.asc
Description: PGP signature

Follow-Ups:
- Re: [PATCH -next v8 0/2] support allocating crashkernel above 4G explicitly on riscv
  - From: chenjiahao (C)

References:
- [PATCH -next v8 0/2] support allocating crashkernel above 4G explicitly on riscv
  - From: Chen Jiahao

Prev by Date: Re: [PATCH 01/18] pwm: Provide devm_pwmchip_alloc() function
Next by Date: Re: [PATCH drm-misc-next v8 11/12] drm/nouveau: implement new VM_BIND uAPI
Previous by thread: [PATCH -next v8 1/2] riscv: kdump: Implement crashkernel=X,[high,low]
Next by thread: Re: [PATCH -next v8 0/2] support allocating crashkernel above 4G explicitly on riscv
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Security] [Netfilter] [Bugtraq] [Linux FS] [Yosemite Forum] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Samba] [Video 4 Linux] [Device Mapper] [Linux Resources]

Powered by Linux