From: KernelCI bot <bot@kernelci•org>
To: kernelci-results@groups•io
Cc: regressions@lists•linux.dev, gus@collabora•com,
linux-next@vger•kernel.org
Subject: [REGRESSION] next/master: (build) ./arch/mips/include/asm/cacheflush.h:42:34: error: passing argumen...
Date: Thu, 21 Aug 2025 06:59:03 -0000 [thread overview]
Message-ID: <175575954332.147.3671353627841122443@16ad3c994827> (raw)
Hello,
New build issue found on next/master:
---
./arch/mips/include/asm/cacheflush.h:42:34: error: passing argument 2 of ‘set_bit’ from incompatible pointer type [-Werror=incompatible-pointer-types] in arch/mips/kernel/asm-offsets.s (arch/mips/kernel/asm-offsets.c) [logspec:kbuild,kbuild.compiler.error]
---
- dashboard: https://d.kernelci.org/i/maestro:dfad1cace3166f976876f942be0d5f653324d85c
- giturl: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
- commit HEAD: 7fa4d8dc380fbd81a9d702a855c50690c9c6442c
- tags: next-20250821
Log excerpt:
=====================================================
from arch/mips/kernel/asm-offsets.c:12:
./arch/mips/include/asm/bitops.h:89:70: note: expected ‘volatile long unsigned int *’ but argument is of type ‘memdesc_flags_t *’
89 | static inline void set_bit(unsigned long nr, volatile unsigned long *addr)
| ~~~~~~~~~~~~~~~~~~~~~~~~^~~~
./arch/mips/include/asm/cacheflush.h: In function ‘flush_dcache_page’:
./arch/mips/include/asm/cacheflush.h:42:34: error: passing argument 2 of ‘set_bit’ from incompatible pointer type [-Werror=incompatible-pointer-types]
42 | set_bit(PG_dcache_dirty, &(folio)->flags)
| ^~~~~~~~~~~~~~~
| |
| memdesc_flags_t *
./arch/mips/include/asm/cacheflush.h:70:17: note: in expansion of macro ‘folio_set_dcache_dirty’
70 | folio_set_dcache_dirty(page_folio(page));
| ^~~~~~~~~~~~~~~~~~~~~~
./arch/mips/include/asm/bitops.h:89:70: note: expected ‘volatile long unsigned int *’ but argument is of type ‘memdesc_flags_t *’
89 | static inline void set_bit(unsigned long nr, volatile unsigned long *addr)
| ~~~~~~~~~~~~~~~~~~~~~~~~^~~~
cc1: some warnings being treated as errors
=====================================================
# Builds where the incident occurred:
## 32r2el_defconfig on (mips):
- compiler: gcc-12
- dashboard: https://d.kernelci.org/build/maestro:68a6c16c233e484a3fa4cedd
## 32r2el_defconfig+allnoconfig on (mips):
- compiler: gcc-12
- dashboard: https://d.kernelci.org/build/maestro:68a6c169233e484a3fa4ceda
#kernelci issue maestro:dfad1cace3166f976876f942be0d5f653324d85c
Reported-by: kernelci.org bot <bot@kernelci•org>
--
This is an experimental report format. Please send feedback in!
Talk to us at kernelci@lists•linux.dev
Made with love by the KernelCI team - https://kernelci.org
reply other threads:[~2025-08-21 6:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=175575954332.147.3671353627841122443@16ad3c994827 \
--to=bot@kernelci$(echo .)org \
--cc=gus@collabora$(echo .)com \
--cc=kernelci-results@groups$(echo .)io \
--cc=kernelci@lists$(echo .)linux.dev \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=regressions@lists$(echo .)linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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