From: Mike Rapoport <rppt@kernel.org>
To: "Michał Cłapiński" <mclapinski@google.com>
Cc: Pasha Tatashin <pasha.tatashin@soleen.com>,
Pratyush Yadav <pratyush@kernel.org>,
Alexander Graf <graf@amazon.com>,
Evangelos Petrongonas <epetron@amazon.de>,
kexec@lists.infradead.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] kho: align kho_scratch to MAX_ORDER_NR_PAGES pages
Date: Mon, 3 Aug 2026 14:28:17 +0300 [thread overview]
Message-ID: <anB7UXU0DduiJ-Lw@kernel.org> (raw)
In-Reply-To: <CAAi7L5dE=oROWR0mTknPyjnL-XRXuCUsfHSiGh7yUqWCSzE5PQ@mail.gmail.com>
On Mon, Aug 03, 2026 at 12:14:18PM +0200, Michał Cłapiński wrote:
> On Mon, Jul 20, 2026 at 9:45 AM Mike Rapoport <rppt@kernel.org> wrote:
> >
> > On Fri, 17 Jul 2026 15:40:28 +0200, Michal Clapinski wrote:
> > > kho: align kho_scratch to MAX_ORDER_NR_PAGES pages
> >
> > Applied to fixes branch of liveupdate/linux.git tree, thanks!
> >
> > [1/1] kho: align kho_scratch to MAX_ORDER_NR_PAGES pages
> > commit: c553c774c9715e1c92c48b342f30d60601693fb4
> >
> > tree: https://git.kernel.org/pub/scm/linux/kernel/git/liveupdate/linux
> > branch: fixes
>
> Hey,
> I see that this change (merged 2 weeks ago) didn't make it into linux
> rc6.
I had a really busy week last week, sorry for the delay.
> Do we need to do something manually to get it into the nearest
> release?
I already did :)
https://lore.kernel.org/all/20260803112452.1793120-1-rppt@kernel.org/
> Thanks.
--
Sincerely yours,
Mike.
prev parent reply other threads:[~2026-08-03 11:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-17 13:40 [PATCH v2] kho: align kho_scratch to MAX_ORDER_NR_PAGES pages Michal Clapinski
2026-07-17 16:21 ` Pasha Tatashin
2026-07-17 17:25 ` Michał Cłapiński
2026-07-20 7:44 ` Mike Rapoport
2026-08-03 10:14 ` Michał Cłapiński
2026-08-03 11:28 ` Mike Rapoport [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=anB7UXU0DduiJ-Lw@kernel.org \
--to=rppt@kernel.org \
--cc=epetron@amazon.de \
--cc=graf@amazon.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mclapinski@google.com \
--cc=pasha.tatashin@soleen.com \
--cc=pratyush@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