From: Andrew Morton <akpm@linux-foundation.org>
To: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, "Liam R . Howlett" <Liam.Howlett@oracle.com>,
Vlastimil Babka <vbabka@suse.cz>,
Matthew Wilcox <willy@infradead.org>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Christian Brauner <brauner@kernel.org>, Jan Kara <jack@suse.cz>,
Eric Biederman <ebiederm@xmission.com>,
Kees Cook <kees@kernel.org>,
Suren Baghdasaryan <surenb@google.com>
Subject: Re: [PATCH 0/7] Make core VMA operations internal and testable
Date: Wed, 3 Jul 2024 14:43:45 -0700 [thread overview]
Message-ID: <20240703144345.530d82e0f337fe7b57704df6@linux-foundation.org> (raw)
In-Reply-To: <1a41caa5-561e-415f-85f3-01b52b233506@lucifer.local>
On Wed, 3 Jul 2024 21:33:00 +0100 Lorenzo Stoakes <lorenzo.stoakes@oracle.com> wrote:
> >
> > > 51 files changed, 3914 insertions(+), 2453 deletions(-)
> >
> > eep. The best time for me to merge this is late in the -rc cycle so
> > the large skew between mainline and mm.git doesn't spend months
> > hampering ongoing development. But that merge time is right now.
>
> Argh. Well, the numbers are scary, but it's _mostly_ moving code around
> with some pretty straightforward refactorings and adding a bunch of
> userland code that won't impact kernels at all.
>
> So I'd argue this is less crazy in size than it might seem...
OK, let's leave it a couple of days for some feedback then decide.
It's still a couple of weeks until we go upstream.
next prev parent reply other threads:[~2024-07-03 21:43 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-03 11:57 Lorenzo Stoakes
2024-07-03 11:57 ` [PATCH 1/7] userfaultfd: move core VMA manipulation logic to mm/userfaultfd.c Lorenzo Stoakes
2024-07-03 11:57 ` [PATCH 2/7] mm: move vma_modify() and helpers to internal header Lorenzo Stoakes
2024-07-03 11:57 ` [PATCH 3/7] mm: move vma_shrink(), vma_expand() " Lorenzo Stoakes
2024-07-03 11:57 ` [PATCH 4/7] mm: move internal core VMA manipulation functions to own file Lorenzo Stoakes
2024-07-03 11:57 ` [PATCH 5/7] MAINTAINERS: Add entry for new VMA files Lorenzo Stoakes
2024-07-04 7:39 ` Vlastimil Babka
2024-07-04 9:49 ` Lorenzo Stoakes
2024-07-03 11:57 ` [PATCH 6/7] tools: separate out shared radix-tree components Lorenzo Stoakes
2024-07-03 11:57 ` [PATCH 7/7] tools: add skeleton code for userland testing of VMA logic Lorenzo Stoakes
2024-07-04 5:59 ` SeongJae Park
2024-07-04 10:51 ` Lorenzo Stoakes
2024-07-04 11:44 ` Lorenzo Stoakes
2024-07-03 20:26 ` [PATCH 0/7] Make core VMA operations internal and testable Andrew Morton
2024-07-03 20:33 ` Lorenzo Stoakes
2024-07-03 21:43 ` Andrew Morton [this message]
2024-07-03 22:56 ` SeongJae Park
2024-07-03 23:24 ` Lorenzo Stoakes
2024-07-04 0:31 ` SeongJae Park
2024-07-04 1:26 ` Andrew Morton
2024-07-04 7:10 ` David Gow
2024-07-04 10:18 ` 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=20240703144345.530d82e0f337fe7b57704df6@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=Liam.Howlett@oracle.com \
--cc=brauner@kernel.org \
--cc=ebiederm@xmission.com \
--cc=jack@suse.cz \
--cc=kees@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=surenb@google.com \
--cc=vbabka@suse.cz \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.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