From: Breno Leitao <leitao@debian.org>
To: SeongJae Park <sj@kernel.org>
Cc: Alexander Graf <graf@amazon.com>, Mike Rapoport <rppt@kernel.org>,
Pasha Tatashin <pasha.tatashin@soleen.com>,
Pratyush Yadav <pratyush@kernel.org>,
linux-kernel@vger.kernel.org, kexec@lists.infradead.org,
linux-mm@kvack.org, usamaarif642@gmail.com, rmikey@meta.com,
clm@fb.com, riel@surriel.com, kernel-team@meta.com
Subject: Re: [PATCH v3 0/2] kho: history: track previous kernel version and kexec boot count
Date: Fri, 9 Jan 2026 03:00:13 -0800 [thread overview]
Message-ID: <irmvsaihncn5pj62iylpqsp4idauakyoiy2xhazh5huomnveb7@qhgrjmbkb55q> (raw)
In-Reply-To: <20260109014559.68677-1-sj@kernel.org>
Hello SJ,
On Thu, Jan 08, 2026 at 05:45:58PM -0800, SeongJae Park wrote:
> On Thu, 08 Jan 2026 08:40:57 -0800 Breno Leitao <leitao@debian.org> wrote:
>
> > Use Kexec Handover (KHO) to pass the previous kernel's version string
> > and the number of kexec reboots since the last cold boot to the next
> > kernel, and print it at boot time.
> >
> > Example
> > =======
> > [ 0.000000] Linux version 6.19.0-rc3-upstream-00047-ge5d992347849
> > ...
> > [ 0.000000] KHO: exec from: 6.19.0-rc4-next-20260107upstream-00004-g3071b0dc4498 (count 1)
>
> Nit. The above snippet uses tabs for first two lines, while the third line
> uses spaces. I don't really mind this of course, please feel free to ignore.
> I just wanted to prove I did read your cover letter ;)
Thanks for reading it very carefully.
[...]
> Sounds this feature will be useful! Thank you for detailed cover letter.
>
> > Signed-off-by: Breno Leitao <leitao@debian.org>
>
> The patches also look good to me. For the series,
>
> Acked-by: SeongJae Park <sj@kernel.org>
>
> > ---
> > Changes from v1 to RFC
>
> Nit. You mean "from RFC (v1) to v2"? Again, I don't really mind this trivial
> thing, so please feel free to ignore.
Ack, my fault here. I am using b4, and I need to learn how to deal with
RFC -> V1 ambiguity better.
If there is a need to update this patchset, I will get them fixed in the
next version.
Thanks for the review,
--breno
prev parent reply other threads:[~2026-01-09 11:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-08 16:40 Breno Leitao
2026-01-08 16:40 ` [PATCH v3 1/2] kho: history: track previous kernel version Breno Leitao
2026-01-08 16:40 ` [PATCH v3 2/2] kho: history: track kexec boot counter Breno Leitao
2026-01-09 1:45 ` [PATCH v3 0/2] kho: history: track previous kernel version and kexec boot count SeongJae Park
2026-01-09 11:00 ` Breno Leitao [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=irmvsaihncn5pj62iylpqsp4idauakyoiy2xhazh5huomnveb7@qhgrjmbkb55q \
--to=leitao@debian.org \
--cc=clm@fb.com \
--cc=graf@amazon.com \
--cc=kernel-team@meta.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pasha.tatashin@soleen.com \
--cc=pratyush@kernel.org \
--cc=riel@surriel.com \
--cc=rmikey@meta.com \
--cc=rppt@kernel.org \
--cc=sj@kernel.org \
--cc=usamaarif642@gmail.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