From: Wei Yang <richard.weiyang@gmail.com>
To: rppt@kernel.org, richard.weiyang@gmail.com
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: [PATCH v2 1/5] memblock test: fix implicit declaration of function 'virt_to_phys'
Date: Mon, 29 Jul 2024 01:47:21 +0000 [thread overview]
Message-ID: <20240729014725.29839-1-richard.weiyang@gmail.com> (raw)
Commit 94ff46de4a73 ("memblock: Move late alloc warning down to phys
alloc") introduce the usage of virt_to_phys(), which is not defined in
memblock tests.
Define it in mm.h to fix the build error.
Signed-off-by: Wei Yang <richard.weiyang@gmail.com>
---
v2: move definition to mm.h
---
tools/include/linux/mm.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/tools/include/linux/mm.h b/tools/include/linux/mm.h
index cad4f2927983..9db45c5d00fc 100644
--- a/tools/include/linux/mm.h
+++ b/tools/include/linux/mm.h
@@ -20,6 +20,8 @@
#define pfn_to_page(pfn) ((void *)((pfn) * PAGE_SIZE))
#define phys_to_virt phys_to_virt
+#define virt_to_phys(p) ((unsigned long)p)
+
static inline void *phys_to_virt(unsigned long address)
{
return __va(address);
--
2.34.1
next reply other threads:[~2024-07-29 1:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-29 1:47 Wei Yang [this message]
2024-07-29 1:47 ` [PATCH v2 2/5] memblock test: add the definition of __setup() Wei Yang
2024-07-29 1:47 ` [PATCH v2 3/5] memblock test: fix implicit declaration of function 'memparse' Wei Yang
2024-07-29 1:47 ` [PATCH v2 4/5] memblock test: fix implicit declaration of function 'isspace' Wei Yang
2024-07-29 1:47 ` [PATCH v2 5/5] memblock test: fix implicit declaration of function 'strscpy' Wei Yang
2024-07-29 5:37 ` [PATCH v2 1/5] memblock test: fix implicit declaration of function 'virt_to_phys' Mike Rapoport
2024-08-01 0:07 ` Wei Yang
2024-08-01 6:09 ` Mike Rapoport
2024-08-02 0:53 ` Wei Yang
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=20240729014725.29839-1-richard.weiyang@gmail.com \
--to=richard.weiyang@gmail.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).