From: Chen Pei <cp0613@linux.alibaba.com>
To: rppt@kernel.org
Cc: alex@ghiti.fr, graf@amazon.com, guoren@kernel.org,
kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org, linux-mm@kvack.org,
linux-riscv@lists.infradead.org, palmer@dabbelt.com,
pasha.tatashin@soleen.com, pjw@kernel.org, pratyush@kernel.org,
shuah@kernel.org
Subject: Re: [PATCH v2 1/5] kho: Do not translate the handover FDT address in is_kho_boot()
Date: Fri, 6 Nov 2026 11:41:40 +0800 [thread overview]
Message-ID: <20261106034153.1462-1-cp0613@linux.alibaba.com> (raw)
In-Reply-To: <aux_dPnvXk3LYDxs@kernel.org>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=y, Size: 614 bytes --]
> There was very similar patch:
> https://lore.kernel.org/all/20261023054518.3258350-1-gthelen@google.com
> and while both Greg's and your patch are correct they both have that wall
> of text with too many details commit messages that I don't like.
Hi Mike,
Thanks for the pointer. Greg's change is the same one,and his post
predates the fix in my series and already has Pratyush's review tag
on it. I will drop patch 1 in the next revision.
On the commit messages: they do restate what the diff already shows.
That comes out, and I will trim the other patches in the series the
same way.
Best regards,
Chen
next prev parent reply other threads:[~2026-11-06 3:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-03 8:09 [PATCH v2 0/5] riscv: Enable kexec handover and live update Chen Pei
2026-11-03 8:09 ` [PATCH v2 1/5] kho: Do not translate the handover FDT address in is_kho_boot() Chen Pei
2026-11-05 13:07 ` Mike Rapoport
2026-11-06 3:41 ` Chen Pei [this message]
2026-11-03 8:09 ` [PATCH v2 2/5] riscv: Call early_ioremap_setup() before parsing the DTB Chen Pei
2026-11-03 8:09 ` [PATCH v2 3/5] riscv: Add support for kexec handover (KHO) Chen Pei
2026-11-03 8:09 ` [PATCH v2 4/5] selftests: kho: Add riscv support Chen Pei
2026-11-05 13:08 ` Mike Rapoport
2026-11-03 8:09 ` [PATCH v2 5/5] selftests: liveupdate: " Chen Pei
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=20261106034153.1462-1-cp0613@linux.alibaba.com \
--to=cp0613@linux.alibaba.com \
--cc=alex@ghiti.fr \
--cc=graf@amazon.com \
--cc=guoren@kernel.org \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=pasha.tatashin@soleen.com \
--cc=pjw@kernel.org \
--cc=pratyush@kernel.org \
--cc=rppt@kernel.org \
--cc=shuah@kernel.org \
/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
all inboxes | Powered by JetHome®