From: Pratyush Yadav <pratyush@kernel.org>
To: tarunsahu@google.com
Cc: Alexander Graf <graf@amazon.com>,
Pratyush Yadav <pratyush@kernel.org>,
Mike Rapoport <rppt@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Pasha Tatashin <pasha.tatashin@soleen.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
kexec@lists.infradead.org
Subject: Re: [PATCH v2 0/2] luo: migrate serialized_data to type-safe KHO pointers
Date: Fri, 19 Jun 2026 16:11:32 +0200 [thread overview]
Message-ID: <2vxzmrwqoc17.fsf@kernel.org> (raw)
In-Reply-To: <9huzv7beloza.fsf@tarunix.c.googlers.com> (tarunsahu@google.com's message of "Fri, 19 Jun 2026 12:00:09 +0000")
On Fri, Jun 19 2026, tarunsahu@google.com wrote:
> +Mike, +Pasha
>
> This is currently rebased on top of mailine, also can be applied to
> liveupdate/fixes with no conflict. I would like to know which release
> cycle we are targeting for this, so That I can rebase it accordingly?
>
> As for liveupdate/next, it needs some conlfict resolution.
Base it on liveupdate/next after the merge window. Since nothing is
actively broken (as far as I can tell), I don't think we should take it
via fixes. We should do it via the 7.3 merge window.
>
> Tarun Sahu <tarunsahu@google.com> writes:
>
>> Covvert raw serialized_data to KHO serializeable pointer (KHOSER_PTR).
>> This series also takes care of resolving the bug with memfd of using
>> phys_to_virt before checking the args->serialized_data value.
[...]
--
Regards,
Pratyush Yadav
prev parent reply other threads:[~2026-06-19 14:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-16 13:23 [PATCH v2 0/2] luo: migrate serialized_data to type-safe KHO pointers Tarun Sahu
2026-06-16 13:23 ` [PATCH v2 1/2] kho: add KHOSER_COPY_TYPE(UN)SAFE for phys copy Tarun Sahu
2026-06-16 13:23 ` [PATCH v2 2/2] luo: Update serialized data to KHOSER_PTR Tarun Sahu
2026-06-19 12:00 ` [PATCH v2 0/2] luo: migrate serialized_data to type-safe KHO pointers tarunsahu
2026-06-19 14:11 ` Pratyush Yadav [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=2vxzmrwqoc17.fsf@kernel.org \
--to=pratyush@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=graf@amazon.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pasha.tatashin@soleen.com \
--cc=rppt@kernel.org \
--cc=tarunsahu@google.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