From: Andrew Morton <akpm@linux-foundation.org>
To: Pratyush Yadav <pratyush@kernel.org>
Cc: Mike Rapoport <rppt@kernel.org>,
Pasha Tatashin <pasha.tatashin@soleen.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH 1/2] liveupdate: luo_file: do not clear serialized_data on unfreeze
Date: Fri, 30 Jan 2026 11:50:04 -0800 [thread overview]
Message-ID: <20260130115004.b530155b27d6d15929bcfa63@linux-foundation.org> (raw)
In-Reply-To: <2vxzv7gj7wv7.fsf@kernel.org>
On Fri, 30 Jan 2026 19:56:28 +0100 Pratyush Yadav <pratyush@kernel.org> wrote:
> >> Fixes: 7c722a7f44e0 ("liveupdate: luo_file: implement file systems callbacks")
> >> Signed-off-by: Pratyush Yadav (Google) <pratyush@kernel.org>
> >
> > Reviewed-by: Mike Rapoport (Microsoft) <rppt@kernel.org>
>
> Thanks.
>
> Andrew, do you mind taking this patch in v6.19-rc8/v6.19 hotfixes?
Yep, that's where it was.
> The
> second patch needs a re-roll and I don't think I would be able to do it
> this week.
>
> This is an independent fix and I see no reason to block this waiting for
> the other one.
OK, I moved "liveupdate: luo_file: remember retrieve() status" to
tail-of-everything and added a note that a new version is expected.
next prev parent reply other threads:[~2026-01-30 19:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-26 23:02 [PATCH 0/2] liveupdate: fixes in error handling Pratyush Yadav
2026-01-26 23:02 ` [PATCH 1/2] liveupdate: luo_file: do not clear serialized_data on unfreeze Pratyush Yadav
2026-01-28 11:19 ` Mike Rapoport
2026-01-30 18:56 ` Pratyush Yadav
2026-01-30 19:50 ` Andrew Morton [this message]
2026-02-02 11:14 ` Pratyush Yadav
2026-01-26 23:02 ` [PATCH 2/2] liveupdate: luo_file: remember retrieve() status Pratyush Yadav
2026-01-28 11:37 ` Mike Rapoport
2026-02-10 13:30 ` Pratyush Yadav
2026-01-31 15:31 ` Pasha Tatashin
2026-02-10 13:31 ` Pratyush Yadav
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=20260130115004.b530155b27d6d15929bcfa63@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pasha.tatashin@soleen.com \
--cc=pratyush@kernel.org \
--cc=rppt@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