From: sashiko-bot@kernel.org
To: "Anshuman Khandual" <anshuman.khandual@arm.com>
Cc: linux-s390@vger.kernel.org, "Heiko Carstens" <hca@linux.ibm.com>,
"Vasily Gorbik" <gor@linux.ibm.com>,
"Alexander Gordeev" <agordeev@linux.ibm.com>,
"Christian Borntraeger" <borntraeger@linux.ibm.com>
Subject: Re: [PATCH 1/3] s390/mm: Drop all pxdp_get()
Date: Wed, 23 Sep 2026 04:42:06 +0000 [thread overview]
Message-ID: <20260923044206.C18271F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260923043226.331880-2-anshuman.khandual@arm.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] mm: s390 build failure due to conflicting types for pxdp_get() helpers
--
commit f8684b75ea3db8facc582e1cba2e98f8430ce2eb
Author: Anshuman Khandual <anshuman.khandual@arm.com>
s390/mm: Drop all pxdp_get()
This commit removes the s390 platform-specific pxdp_get() helpers, relying
instead on the generic definitions in the core MM headers. It also adds
forward declarations for these generic helpers to satisfy local dependencies.
> diff --git a/arch/s390/include/asm/pgtable.h b/arch/s390/include/asm/pgtable.h
> index e882663a58e77..0a0b0ec42b624 100644
> --- a/arch/s390/include/asm/pgtable.h
> +++ b/arch/s390/include/asm/pgtable.h
> @@ -25,6 +25,11 @@
> #include <asm/page.h>
> #include <asm/uv.h>
>
> +static inline pte_t ptep_get(const pte_t *ptep);
> +static inline pud_t pudp_get(const pud_t *pudp);
> +static inline p4d_t p4dp_get(const p4d_t *p4dp);
> +static inline pgd_t pgdp_get(const pgd_t *pgdp);
[Severity: Low]
Does this cause a build failure on s390 due to conflicting types?
These forward declarations define the parameters as const pointers, but the
generic fallback definitions specify a non-const pointer. For example, in
include/linux/pgtable.h:
static inline pte_t ptep_get(pte_t *ptep)
{
return READ_ONCE(*ptep);
}
This mismatch between const pte_t * and pte_t * appears to result in a fatal
compile-time error during the build.
[ ... ]
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260923043226.331880-1-anshuman.khandual@arm.com?part=1
next prev parent reply other threads:[~2026-09-23 4:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-23 4:32 [PATCH 0/3] arch/mm: Drop similar platform overrides for pxdp_get() Anshuman Khandual
2026-09-23 4:32 ` [PATCH 1/3] s390/mm: Drop all pxdp_get() Anshuman Khandual
2026-09-23 4:42 ` sashiko-bot [this message]
2026-09-23 9:16 ` Heiko Carstens
2026-09-23 12:12 ` Anshuman Khandual
2026-09-23 14:32 ` Heiko Carstens
2026-09-24 2:37 ` Anshuman Khandual
2026-09-23 4:32 ` [PATCH 2/3] loongarch/mm: " Anshuman Khandual
2026-09-23 4:41 ` sashiko-bot
2026-09-23 4:32 ` [PATCH 3/3] parisc/mm: " Anshuman Khandual
2026-09-23 4:42 ` sashiko-bot
-- strict thread matches above, loose matches on Subject: below --
2026-09-19 10:13 [PATCH 0/3] arch/mm: Drop similar platform overrides for pxdp_get() Anshuman Khandual
2026-09-19 10:13 ` [PATCH 1/3] s390/mm: Drop all pxdp_get() Anshuman Khandual
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=20260923044206.C18271F000FF@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=agordeev@linux.ibm.com \
--cc=anshuman.khandual@arm.com \
--cc=borntraeger@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=linux-s390@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.