From: Naresh Kamboju <naresh.kamboju@linaro.org>
To: lkft-triage@lists.linaro.org,
open list <linux-kernel@vger.kernel.org>,
Linux Regressions <regressions@lists.linux.dev>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
linux-mm <linux-mm@kvack.org>
Cc: Dan Carpenter <dan.carpenter@linaro.org>,
Anders Roxell <anders.roxell@linaro.org>,
Arnd Bergmann <arnd@arndb.de>,
"Naveen N. Rao" <naveen.n.rao@linux.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: mm: gup.c:2827:22: error: conflicting types for 'try_grab_folio_fast'; have 'struct folio
Date: Mon, 1 Jul 2024 15:35:23 +0530 [thread overview]
Message-ID: <CA+G9fYve66bw-4xVrJnfeXtRV1et1UhEZMFAvvTXbKB2-m--fg@mail.gmail.com> (raw)
The powerpc build failures noticed on Linux next-20240628 tag.
Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
Regressions found on powerpc:
- gcc-13-maple_defconfig
- gcc-13-cell_defconfig
- clang-nightly-maple_defconfig
- gcc-8-defconfig
- gcc-8-tqm8xx_defconfig
- clang-18-tqm8xx_defconfig
- gcc-8-maple_defconfig
- clang-nightly-cell_defconfig
- clang-18-maple_defconfig
- gcc-13-defconfig
- clang-18-defconfig
- clang-nightly-defconfig
- gcc-13-tqm8xx_defconfig
- clang-nightly-tqm8xx_defconfig
- gcc-8-cell_defconfig
- clang-18-cell_defconfig
Build error:
---
mm/gup.c: In function 'gup_hugepte':
mm/gup.c:525:25: error: implicit declaration of function
'try_grab_folio_fast'; did you mean 'try_grab_folio'?
[-Werror=implicit-function-declaration]
525 | folio = try_grab_folio_fast(page, refs, flags);
| ^~~~~~~~~~~~~~~~~~~
| try_grab_folio
mm/gup.c:525:23: warning: assignment to 'struct folio *' from 'int'
makes pointer from integer without a cast [-Wint-conversion]
525 | folio = try_grab_folio_fast(page, refs, flags);
| ^
mm/gup.c: At top level:
mm/gup.c:2827:22: error: conflicting types for 'try_grab_folio_fast';
have 'struct folio *(struct page *, int, unsigned int)'
2827 | static struct folio *try_grab_folio_fast(struct page *page, int refs,
| ^~~~~~~~~~~~~~~~~~~
mm/gup.c:525:25: note: previous implicit declaration of
'try_grab_folio_fast' with type 'int()'
525 | folio = try_grab_folio_fast(page, refs, flags);
| ^~~~~~~~~~~~~~~~~~~
cc1: some warnings being treated as errors
Steps to reproduce:
----
# tuxmake --runtime podman --target-arch powerpc --toolchain gcc-13
--kconfig cell_defconfig
metadata:
----
git_describe: next-20240628
git_repo: https://gitlab.com/Linaro/lkft/mirrors/next/linux-next
git_short_log: 1eb586a9782c ("Add linux-next specific files for 20240628")
arch: powerpc
toolchain: gcc-13 and clang-18
Links:
- https://storage.tuxsuite.com/public/linaro/lkft/builds/2iWYcbTLGMcGuxl7caQ3jwv9C4a/
- https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20240628/testrun/24464887/suite/build/test/gcc-13-cell_defconfig/details/
- https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20240628/testrun/24464887/suite/build/test/gcc-13-cell_defconfig/log
--
Linaro LKFT
https://lkft.linaro.org
reply other threads:[~2024-07-01 10:05 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=CA+G9fYve66bw-4xVrJnfeXtRV1et1UhEZMFAvvTXbKB2-m--fg@mail.gmail.com \
--to=naresh.kamboju@linaro.org \
--cc=akpm@linux-foundation.org \
--cc=anders.roxell@linaro.org \
--cc=arnd@arndb.de \
--cc=dan.carpenter@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=lkft-triage@lists.linaro.org \
--cc=naveen.n.rao@linux.ibm.com \
--cc=regressions@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox