From: Johannes Berg <johannes@sipsolutions.net>
To: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
Hajime Tazaki <thehajime@gmail.com>
Cc: linux-um@lists.infradead.org, ricarkol@google.com,
Liam.Howlett@oracle.com, richard@nod.at,
anton.ivanov@cambridgegreys.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v7 00/13] nommu UML
Date: Wed, 30 Apr 2025 11:51:47 +0200 [thread overview]
Message-ID: <0837b343960cc6392df4a04b974a2ebca4b60b9f.camel@sipsolutions.net> (raw)
In-Reply-To: <7271fdc2-5f3f-459d-ad64-b0275265fe2a@lucifer.local>
On Tue, 2025-04-29 at 14:23 +0100, Lorenzo Stoakes wrote:
> Thanks, appreciate the response. I would say send a v8 that's rebased to
> make life easier for maintainers :) if you already have it ready to go that
> is!
There probably haven't been that many patches since, but I guess why not
:)
I was sort of hoping to get the seccomp patches from Benjamin - that
have been waiting far longer - in first to see what overlap if any there
might be, but I think he and Hajime have already concluded there wasn't
all that much overlap anyway.
But it's good to hear that it'd be useful to you.
johannes
next prev parent reply other threads:[~2025-04-30 9:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1737348399.git.thehajime@gmail.com>
2025-01-20 6:00 ` [PATCH v7 02/13] x86/um: nommu: elf loader for fdpic Hajime Tazaki
2025-04-25 13:49 ` [PATCH v7 00/13] nommu UML Lorenzo Stoakes
2025-04-27 3:49 ` Hajime Tazaki
2025-04-29 13:23 ` Lorenzo Stoakes
2025-04-30 9:51 ` Johannes Berg [this message]
2025-05-01 10:40 ` Lorenzo Stoakes
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=0837b343960cc6392df4a04b974a2ebca4b60b9f.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=Liam.Howlett@oracle.com \
--cc=anton.ivanov@cambridgegreys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-um@lists.infradead.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=ricarkol@google.com \
--cc=richard@nod.at \
--cc=thehajime@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