From: "chenjiahao (C)" <chenjiahao16@huawei.com>
To: Conor Dooley <conor.dooley@microchip.com>
Cc: Conor Dooley <conor@kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-riscv@lists.infradead.org>, <kexec@lists.infradead.org>,
<linux-doc@vger.kernel.org>, <paul.walmsley@sifive.com>,
<palmer@dabbelt.com>, <guoren@kernel.org>, <heiko@sntech.de>,
<bjorn@rivosinc.com>, <alex@ghiti.fr>,
<akpm@linux-foundation.org>, <atishp@rivosinc.com>,
<bhe@redhat.com>, <thunder.leizhen@huawei.com>,
<horms@kernel.org>
Subject: Re: [PATCH -next v8 0/2] support allocating crashkernel above 4G explicitly on riscv
Date: Wed, 26 Jul 2023 17:30:49 +0800 [thread overview]
Message-ID: <43731b35-c076-6d01-ad83-764fb2e9a8f0@huawei.com> (raw)
In-Reply-To: <20230726-affix-employed-319aada685e7@wendy>
On 2023/7/26 14:45, Conor Dooley wrote:
> On Wed, Jul 26, 2023 at 10:20:00AM +0800, chenjiahao (C) wrote:
>> 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?
> There's some difference between linux-next and riscv/for-next that
> prevents the patchwork automation from applying the patches.
Oh, I see. There is definitely a difference, since linux-next applied
a bugfix patch b690e266dae2 ("riscv: mm: fix truncation warning on RV32")
recently, whereas riscv/for-next didn't. I have worked on a wrong base
and thanks for reminding :)
I will rebase onto riscv/for-next and post my v9 pathset soon, please
check over there.
Thanks,
Jiahao
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
prev parent reply other threads:[~2023-07-26 9:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-25 21:44 [PATCH -next v8 0/2] support allocating crashkernel above 4G explicitly on riscv Chen Jiahao
2023-07-25 21:44 ` [PATCH -next v8 1/2] riscv: kdump: Implement crashkernel=X,[high,low] Chen Jiahao
2023-07-25 21:44 ` [PATCH -next v8 2/2] docs: kdump: Update the crashkernel description for riscv Chen Jiahao
2023-07-25 21:48 ` [PATCH -next v8 0/2] support allocating crashkernel above 4G explicitly on riscv Conor Dooley
2023-07-26 2:20 ` chenjiahao (C)
2023-07-26 6:45 ` Conor Dooley
2023-07-26 9:30 ` chenjiahao (C) [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=43731b35-c076-6d01-ad83-764fb2e9a8f0@huawei.com \
--to=chenjiahao16@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=alex@ghiti.fr \
--cc=atishp@rivosinc.com \
--cc=bhe@redhat.com \
--cc=bjorn@rivosinc.com \
--cc=conor.dooley@microchip.com \
--cc=conor@kernel.org \
--cc=guoren@kernel.org \
--cc=heiko@sntech.de \
--cc=horms@kernel.org \
--cc=kexec@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=thunder.leizhen@huawei.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox