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>,
SeongJae Park <sj@kernel.org>, Shuah Khan <shuah@kernel.org>,
Brendan Higgins <brendanhiggins@google.com>,
David Gow <davidgow@google.com>, Rae Moar <rmoar@google.com>
Subject: Re: [PATCH v3 6/7] tools: separate out shared radix-tree components
Date: Sun, 28 Jul 2024 13:15:03 -0700 [thread overview]
Message-ID: <20240728131503.18f2f41bc15d2fdaddf5fc75@linux-foundation.org> (raw)
In-Reply-To: <d5905fa6f25b159a156a5a6a87c5b1ac25568c5b.1721648367.git.lorenzo.stoakes@oracle.com>
On Mon, 22 Jul 2024 12:50:24 +0100 Lorenzo Stoakes <lorenzo.stoakes@oracle.com> wrote:
> The core components contained within the radix-tree tests which provide
> shims for kernel headers and access to the maple tree are useful for
> testing other things, so separate them out and make the radix tree tests
> dependent on the shared components.
>
> This lays the groundwork for us to add VMA tests of the newly introduced
> vma.c file.
>
> ...
>
> tools/testing/{radix-tree => shared}/bitmap.c | 0
Some merge issues have popped up - people have been messing around with
the radix tree test code and not telling us. I'll drop the v3 series -
please redo and resend against 6.11-rc1?
Thanks.
next prev parent reply other threads:[~2024-07-28 20:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-22 11:50 [PATCH v3 0/7] Make core VMA operations internal and testable Lorenzo Stoakes
2024-07-22 11:50 ` [PATCH v3 1/7] userfaultfd: move core VMA manipulation logic to mm/userfaultfd.c Lorenzo Stoakes
2024-07-22 11:50 ` [PATCH v3 2/7] mm: move vma_modify() and helpers to internal header Lorenzo Stoakes
2024-07-22 11:50 ` [PATCH v3 3/7] mm: move vma_shrink(), vma_expand() " Lorenzo Stoakes
2024-07-22 11:50 ` [PATCH v3 4/7] mm: move internal core VMA manipulation functions to own file Lorenzo Stoakes
2024-07-23 16:58 ` SeongJae Park
2024-07-23 17:15 ` Lorenzo Stoakes
2024-07-22 11:50 ` [PATCH v3 5/7] MAINTAINERS: Add entry for new VMA files Lorenzo Stoakes
2024-07-22 11:50 ` [PATCH v3 6/7] tools: separate out shared radix-tree components Lorenzo Stoakes
2024-07-23 9:25 ` Mike Rapoport
2024-07-23 9:35 ` Lorenzo Stoakes
2024-07-25 10:20 ` Lorenzo Stoakes
2024-07-28 20:15 ` Andrew Morton [this message]
2024-07-22 11:50 ` [PATCH v3 7/7] tools: add skeleton code for userland testing of VMA logic Lorenzo Stoakes
2024-07-23 17:20 ` [PATCH v3 0/7] Make core VMA operations internal and testable 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=20240728131503.18f2f41bc15d2fdaddf5fc75@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=Liam.Howlett@oracle.com \
--cc=brauner@kernel.org \
--cc=brendanhiggins@google.com \
--cc=davidgow@google.com \
--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=rmoar@google.com \
--cc=shuah@kernel.org \
--cc=sj@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).