From: Hajime Tazaki <thehajime@gmail.com>
To: tiwei.bie@linux.dev
Cc: Liam.Howlett@oracle.com, hch@infradead.org,
johannes@sipsolutions.net, linux-kernel@vger.kernel.org,
linux-um@lists.infradead.org, ricarkol@google.com
Subject: Re: [PATCH v13 00/13] nommu UML
Date: Fri, 14 Nov 2025 15:47:34 +0900 [thread overview]
Message-ID: <m2a50pxg8p.wl-thehajime@gmail.com> (raw)
In-Reply-To: <20251112163651.3689244-1-tiwei.bie@linux.dev>
On Thu, 13 Nov 2025 01:36:51 +0900,
Tiwei Bie wrote:
> > we haven't seen any functional regressions
> > since this RFC version (which was 6.12 kernel).
>
> I took a quick look at the code. It appears that patch 02/13 will
> break the mmu build when UML_TIME_TRAVEL_SUPPORT is enabled.
thanks, it is my bad on the move the chunk.
will fix it and added to my local test.
-- Hajime
prev parent reply other threads:[~2025-11-14 6:47 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-08 8:05 [PATCH v13 00/13] nommu UML Hajime Tazaki
2025-11-08 8:05 ` [PATCH v13 01/13] x86/um: nommu: elf loader for fdpic Hajime Tazaki
2025-11-08 8:05 ` [PATCH v13 02/13] um: decouple MMU specific code from the common part Hajime Tazaki
2025-11-08 8:05 ` [PATCH v13 03/13] um: nommu: memory handling Hajime Tazaki
2025-11-08 8:05 ` [PATCH v13 04/13] x86/um: nommu: syscall handling Hajime Tazaki
2025-11-08 8:05 ` [PATCH v13 05/13] um: nommu: seccomp syscalls hook Hajime Tazaki
2025-11-08 8:05 ` [PATCH v13 06/13] x86/um: nommu: process/thread handling Hajime Tazaki
2025-11-08 8:05 ` [PATCH v13 07/13] um: nommu: configure fs register on host syscall invocation Hajime Tazaki
2025-11-08 8:05 ` [PATCH v13 08/13] x86/um/vdso: nommu: vdso memory update Hajime Tazaki
2025-11-08 8:05 ` [PATCH v13 09/13] x86/um: nommu: signal handling Hajime Tazaki
2025-11-08 8:05 ` [PATCH v13 10/13] um: change machine name for uname output Hajime Tazaki
2025-11-08 8:05 ` [PATCH v13 11/13] um: nommu: disable SMP on nommu UML Hajime Tazaki
2025-11-08 8:05 ` [PATCH v13 12/13] um: nommu: add documentation of " Hajime Tazaki
2025-11-08 8:05 ` [PATCH v13 13/13] um: nommu: plug nommu code into build system Hajime Tazaki
2025-11-10 9:14 ` [PATCH v13 00/13] nommu UML Christoph Hellwig
2025-11-10 12:18 ` Hajime Tazaki
2025-11-11 8:01 ` Johannes Berg
2025-11-12 8:52 ` Hajime Tazaki
2025-11-12 16:36 ` Tiwei Bie
2025-11-14 6:47 ` Hajime Tazaki [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=m2a50pxg8p.wl-thehajime@gmail.com \
--to=thehajime@gmail.com \
--cc=Liam.Howlett@oracle.com \
--cc=hch@infradead.org \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-um@lists.infradead.org \
--cc=ricarkol@google.com \
--cc=tiwei.bie@linux.dev \
/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;
as well as URLs for NNTP newsgroup(s).