From: peng8420.li@gmail.com
To: linux-mm@kvack.org, akpm@linux-foundation.org
Cc: david@redhat.com, osalvador@suse.de, jgg@ziepe.ca,
jhubbard@nvidia.com, peterx@redhat.com,
linux-kernel@vger.kernel.org, dan.j.williams@intel.com,
"peng8420.li" <peng8420.li@gmail.com>,
"David Hildenbrand (Red Hat)" <david@kernel.org>
Subject: [PATCH v2 2/2] Fix the source file annotation information for the "FOLL_WRITE" macro copied.
Date: Sat, 15 Nov 2025 00:11:27 +0800 [thread overview]
Message-ID: <20251114161127.193707-2-peng8420.li@gmail.com> (raw)
In-Reply-To: <20251114161127.193707-1-peng8420.li@gmail.com>
From: "peng8420.li" <peng8420.li@gmail.com>
The 'FOLL_RITE' of the copied source is located in mm_types. h of mm, not mm. h, so fix it.
Suggested-by: "David Hildenbrand (Red Hat)" <david@kernel.org>
Signed-off-by: peng8420.li <peng8420.li@gmail.com>
---
tools/testing/selftests/mm/gup_test.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/testing/selftests/mm/gup_test.c b/tools/testing/selftests/mm/gup_test.c
index 75f7134d529d..40c1538a17b4 100644
--- a/tools/testing/selftests/mm/gup_test.c
+++ b/tools/testing/selftests/mm/gup_test.c
@@ -17,7 +17,7 @@
#define MB (1UL << 20)
-/* Just the flags we need, copied from mm.h: */
+/* Just the flags we need, copied from the kernel internals. */
#define FOLL_WRITE 0x01 /* check pte is writable */
#define GUP_TEST_FILE "/sys/kernel/debug/gup_test"
--
2.43.0
next prev parent reply other threads:[~2025-11-14 16:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-14 16:11 [PATCH v2 1/2] Remove the "FOLL_TOUCH" test code from gup_test.c peng8420.li
2025-11-14 16:11 ` peng8420.li [this message]
2025-11-14 20:26 ` [PATCH v2 2/2] Fix the source file annotation information for the "FOLL_WRITE" macro copied John Hubbard
2025-11-14 21:41 ` David Hildenbrand (Red Hat)
2025-11-14 20:24 ` [PATCH v2 1/2] Remove the "FOLL_TOUCH" test code from gup_test.c John Hubbard
2025-11-14 21:37 ` David Hildenbrand (Red Hat)
2025-11-14 21:39 ` David Hildenbrand (Red Hat)
2025-11-17 7:09 ` peng li
2025-11-17 7:05 ` peng li
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=20251114161127.193707-2-peng8420.li@gmail.com \
--to=peng8420.li@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=dan.j.williams@intel.com \
--cc=david@kernel.org \
--cc=david@redhat.com \
--cc=jgg@ziepe.ca \
--cc=jhubbard@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=osalvador@suse.de \
--cc=peterx@redhat.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