From: Mike Kravetz <mike.kravetz@oracle.com>
To: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Cc: Michael Ellerman <mpe@ellerman.id.au>,
Ben Dooks <ben.dooks@codethink.co.uk>,
Jason Gunthorpe <jgg@ziepe.ca>,
kbuild@lists.01.org, Andrew Morton <akpm@linux-foundation.org>,
Mike Kravetz <mike.kravetz@oracle.com>
Subject: [PATCH 0/2] hugetlbfs: convert macros to static inline, fix sparse warning
Date: Tue, 12 Nov 2019 11:45:56 -0800 [thread overview]
Message-ID: <20191112194558.139389-1-mike.kravetz@oracle.com> (raw)
The definition for huge_pte_offset() in <linux/hugetlb.h> causes a sparse
warning in the !CONFIG_HUGETLB_PAGE. Fix this as well as converting
all macros in this block of definitions to static inlines for better type
checking.
When making the above changes, build errors were found in powerpc due to
duplicate definitions. A separate powerpc specific patch is included as
a requisite to remove the definitions and get them from <linux/hugetlb.h>.
Cc: kbuild@lists.01.org in an attmept to flush out any other build issues.
Mike Kravetz (2):
powerpc/mm: remove pmd_huge/pud_huge stubs and include hugetlb.h
hugetlbfs: convert macros to static inline, fix sparse warning
.../include/asm/book3s/64/pgtable-4k.h | 3 -
.../include/asm/book3s/64/pgtable-64k.h | 3 -
arch/powerpc/mm/book3s64/radix_pgtable.c | 1 +
include/linux/hugetlb.h | 137 +++++++++++++++---
4 files changed, 116 insertions(+), 28 deletions(-)
--
2.23.0
next reply other threads:[~2019-11-12 19:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-12 19:45 Mike Kravetz [this message]
2019-11-12 19:45 ` [PATCH 1/2] powerpc/mm: remove pmd_huge/pud_huge stubs and include hugetlb.h Mike Kravetz
2019-11-12 19:45 ` [PATCH 2/2] hugetlbfs: convert macros to static inline, fix sparse warning Mike Kravetz
2019-11-12 21:13 ` Joe Perches
2019-11-13 0:11 ` Mike Kravetz
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=20191112194558.139389-1-mike.kravetz@oracle.com \
--to=mike.kravetz@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=ben.dooks@codethink.co.uk \
--cc=jgg@ziepe.ca \
--cc=kbuild@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mpe@ellerman.id.au \
/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