From: Rebecca Mckeever <remckee0@gmail.com>
To: Mike Rapoport <rppt@kernel.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Cc: David Hildenbrand <david@redhat.com>,
Rebecca Mckeever <remckee0@gmail.com>
Subject: [PATCH 5/5] memblock tests: remove completed TODO item
Date: Sun, 25 Sep 2022 16:26:56 -0500 [thread overview]
Message-ID: <5df0bb56e4f32ae2734b7a74c65530d84012b4de.1664138929.git.remckee0@gmail.com> (raw)
In-Reply-To: <cover.1664138928.git.remckee0@gmail.com>
Remove completed item from TODO list.
Signed-off-by: Rebecca Mckeever <remckee0@gmail.com>
---
tools/testing/memblock/TODO | 7 +------
1 file changed, 1 insertion(+), 6 deletions(-)
diff --git a/tools/testing/memblock/TODO b/tools/testing/memblock/TODO
index 33044c634ea7..cb7fac47a643 100644
--- a/tools/testing/memblock/TODO
+++ b/tools/testing/memblock/TODO
@@ -8,10 +8,5 @@ TODO
likely that the current MEM_SIZE won't be enough for these
test cases. Use realloc to adjust the size accordingly.
-2. Add test cases using this functions (implement them for both directions):
- + memblock_alloc_raw()
- + memblock_alloc_exact_nid_raw()
- + memblock_alloc_try_nid_raw()
-
-3. Add tests for memblock_alloc_node() to check if the correct NUMA node is set
+2. Add tests for memblock_alloc_node() to check if the correct NUMA node is set
for the new region
--
2.25.1
prev parent reply other threads:[~2022-09-25 21:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-25 21:26 [PATCH 0/5] memblock tests: add tests for Rebecca Mckeever
2022-09-25 21:26 ` [PATCH 1/5] memblock tests: add range tests for memblock_alloc_exact_nid_raw Rebecca Mckeever
2022-09-25 21:26 ` [PATCH 2/5] memblock tests: add top-down NUMA " Rebecca Mckeever
2022-09-25 21:26 ` [PATCH 3/5] memblock tests: add bottom-up " Rebecca Mckeever
2022-09-25 21:26 ` [PATCH 4/5] memblock tests: add generic " Rebecca Mckeever
2022-09-25 21:26 ` Rebecca Mckeever [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=5df0bb56e4f32ae2734b7a74c65530d84012b4de.1664138929.git.remckee0@gmail.com \
--to=remckee0@gmail.com \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rppt@kernel.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).