[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <96245a6f-cff1-9f2a-1217-4109d9a19291@huawei.com>
Date: Wed, 26 Jul 2023 10:20:00 +0800
From: "chenjiahao (C)" <chenjiahao16@...wei.com>
To: Conor Dooley <conor@...nel.org>
CC: <linux-kernel@...r.kernel.org>, <linux-riscv@...ts.infradead.org>,
<kexec@...ts.infradead.org>, <linux-doc@...r.kernel.org>,
<paul.walmsley@...ive.com>, <palmer@...belt.com>,
<conor.dooley@...rochip.com>, <guoren@...nel.org>,
<heiko@...ech.de>, <bjorn@...osinc.com>, <alex@...ti.fr>,
<akpm@...ux-foundation.org>, <atishp@...osinc.com>,
<bhe@...hat.com>, <thunder.leizhen@...wei.com>, <horms@...nel.org>
Subject: Re: [PATCH -next v8 0/2] support allocating crashkernel above 4G
explicitly on riscv
On 2023/7/26 5:48, Conor Dooley wrote:
> Hey,
>
> Your $subject says -next, but the patch failed to apply to
> riscv/for-next. What was the base for this patchset?
>
> Thanks,
> Conor.
Hi,
My patchset was tested on current linux-next HEAD
(commit ID: 1e25dd777248, tag: next-20230725) and
it seems all ok.
Could you try applying with the base above, or
is there any problem with that base?
Thanks,
Jiahao
Powered by blists - more mailing lists