From: Vlastimil Babka <vbabka@suse.cz>
To: Naresh Kamboju <naresh.kamboju@linaro.org>,
open list <linux-kernel@vger.kernel.org>,
lkft-triage@lists.linaro.org,
Linux Regressions <regressions@lists.linux.dev>,
clang-built-linux <llvm@lists.linux.dev>,
linux-mm <linux-mm@kvack.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Nathan Chancellor <nathan@kernel.org>,
Ben Copeland <benjamin.copeland@linaro.org>,
Arnd Bergmann <arnd@arndb.de>,
Dan Carpenter <dan.carpenter@linaro.org>,
Anders Roxell <anders.roxell@linaro.org>
Subject: Re: next-20250911: mm/slub.c:3960:27: error: a function declaration without a prototype is deprecated in all versions of C void flush_all_rcu_sheaves()
Date: Thu, 11 Sep 2025 10:45:11 +0200 [thread overview]
Message-ID: <fa727f7b-92d5-4fd2-b9cf-a19b27303a22@suse.cz> (raw)
In-Reply-To: <CA+G9fYtUi3bnZ2zycCot6KGeZcn67JAvz=wZm=6f2w9ZnL=0Uw@mail.gmail.com>
On 9/11/25 10:37, Naresh Kamboju wrote:
> The following build warnings / errors noticed on aram arm64 defconfig
> with clang-20 and clang-nightly toolchains on the Linux next-20250911 tag.
>
> Regression Analysis:
> - New regression? yes
> - Reproducibility? yes
>
> Build regression: next-20250911: mm/slub.c:3960:27: error: a function
> declaration without a prototype is deprecated in all versions of C
> void flush_all_rcu_sheaves()
>
> Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
>
> ## Build log
> mm/slub.c:3960:27: error: a function declaration without a prototype
> is deprecated in all versions of C [-Werror,-Wstrict-prototypes]
> 3960 | void flush_all_rcu_sheaves()
> | ^
> | void
> 1 error generated.
Thanks, fixed already for tomorrow's -next
> ## Source
> * Kernel version: 6.17.0-rc5
> * Git tree: https://kernel.googlesource.com/pub/scm/linux/kernel/git/next/linux-next.git
> * Git describe: 6.17.0-rc5-next-20250911
> * Git commit: 8f21d9da46702c4d6951ba60ca8a05f42870fe8f
> * Architectures: arm, arm64, i386, mips, powerpc, riscv, s390
> * Toolchains: clang-20 and clang-nightly
> * clang: Debian clang version 20.1.8
> (++20250809043815+87f0227cb601-1~exp1~20250809163919.3)
> * Kconfigs: defconfig+lkftconfigs
>
> ## Build
> * Build log: https://qa-reports.linaro.org/api/testruns/29853978/log_file/
> * Build details:
> https://regressions.linaro.org/lkft/linux-next-master/next-20250911/build/clang-20-defconfig/
> * Build plan: https://tuxapi.tuxsuite.com/v1/groups/linaro/projects/lkft/builds/32XlFDtH7RdddaA6FHskupLDDSO
> * Build link: https://storage.tuxsuite.com/public/linaro/lkft/builds/32XlFDtH7RdddaA6FHskupLDDSO/
> * Kernel config:
> https://storage.tuxsuite.com/public/linaro/lkft/builds/32XlFDtH7RdddaA6FHskupLDDSO/config
> * Build log details:
> https://regressions.linaro.org/lkft/linux-next-master/next-20250911/log-parser-build-clang/clang-compiler-mm_slub_c-error-a-function-declaration-without-a-prototype-is-deprecated-in-all-versions-of-c/
>
> --
> Linaro LKFT
>
prev parent reply other threads:[~2025-09-11 8:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-11 8:37 Naresh Kamboju
2025-09-11 8:45 ` Vlastimil Babka [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=fa727f7b-92d5-4fd2-b9cf-a19b27303a22@suse.cz \
--to=vbabka@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=anders.roxell@linaro.org \
--cc=arnd@arndb.de \
--cc=benjamin.copeland@linaro.org \
--cc=dan.carpenter@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkft-triage@lists.linaro.org \
--cc=llvm@lists.linux.dev \
--cc=naresh.kamboju@linaro.org \
--cc=nathan@kernel.org \
--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