From: "Matthew Wilcox (Oracle)" <willy@infradead.org>
To: linux-mm@kvack.org, linux-arch@vger.kernel.org
Cc: "Matthew Wilcox (Oracle)" <willy@infradead.org>,
linux-s390@vger.kernel.org, linux-um@lists.infradead.org,
x86@kernel.org
Subject: [PATCH 5/5] mm: Make mk_pte() definition unconditional
Date: Wed, 14 Aug 2024 16:44:25 +0100 [thread overview]
Message-ID: <20240814154427.162475-6-willy@infradead.org> (raw)
In-Reply-To: <20240814154427.162475-1-willy@infradead.org>
All architectures now use the common mk_pte() definition, so we
can remove the condition.
Signed-off-by: Matthew Wilcox (Oracle) <willy@infradead.org>
---
include/linux/pgtable.h | 2 --
1 file changed, 2 deletions(-)
diff --git a/include/linux/pgtable.h b/include/linux/pgtable.h
index 8204ffd87d74..1d46422b79cc 100644
--- a/include/linux/pgtable.h
+++ b/include/linux/pgtable.h
@@ -41,12 +41,10 @@
#define FIRST_USER_ADDRESS 0UL
#endif
-#ifndef mk_pte
static inline pte_t mk_pte(struct page *page, pgprot_t pgprot)
{
return pfn_pte(page_to_pfn(page), pgprot);
}
-#endif
/*
* This defines the generic helper for accessing PMD page
--
2.43.0
prev parent reply other threads:[~2024-08-14 15:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-14 15:44 [PATCH 0/5] Provide a single definition of mk_pte() Matthew Wilcox (Oracle)
2024-08-14 15:44 ` [PATCH 1/5] mm: Introduce a common " Matthew Wilcox (Oracle)
2024-08-15 2:45 ` kernel test robot
2024-08-15 2:45 ` kernel test robot
2024-08-14 15:44 ` [PATCH 2/5] x86: Remove custom " Matthew Wilcox (Oracle)
2024-08-15 4:08 ` kernel test robot
2024-08-14 15:44 ` [PATCH 3/5] um: " Matthew Wilcox (Oracle)
2024-08-14 15:44 ` [PATCH 4/5] s390: " Matthew Wilcox (Oracle)
2024-08-15 12:12 ` Alexander Gordeev
2024-08-22 14:06 ` Alexander Gordeev
2024-08-14 15:44 ` Matthew Wilcox (Oracle) [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=20240814154427.162475-6-willy@infradead.org \
--to=willy@infradead.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-s390@vger.kernel.org \
--cc=linux-um@lists.infradead.org \
--cc=x86@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