From: Naresh Kamboju <naresh.kamboju@linaro.org>
To: open list <linux-kernel@vger.kernel.org>,
lkft-triage@lists.linaro.org,
Linux Regressions <regressions@lists.linux.dev>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Adrian Hunter <adrian.hunter@intel.com>,
Stephen Boyd <sboyd@kernel.org>,
John Stultz <jstultz@google.com>, Arnd Bergmann <arnd@arndb.de>,
Dan Carpenter <dan.carpenter@linaro.org>,
Anders Roxell <anders.roxell@linaro.org>
Subject: tinyconfig: kernel/time/timekeeping.c:286:1: error: no return statement in function returning non-void [-Werror=return-type]
Date: Wed, 10 Apr 2024 16:26:12 +0530 [thread overview]
Message-ID: <CA+G9fYvjdZCW=7ZGxS6A_3bysjQ56YF7S-+PNLQ_8a4DKh1Bhg@mail.gmail.com> (raw)
The powerpc,s390, superSh and sparc tinyconfig builds failed due to
following build
warnings / errors on the Linux next-20240410 with gcc-13 and gcc-11.
List build failures:
---
* s390, build
- gcc-13-tinyconfig - failed
- gcc-8-tinyconfig - failed
* sh, build
- gcc-11-tinyconfig - failed
* sparc, build
- gcc-11-tinyconfig - failed
* mips, build
- gcc-12-tinyconfig - failed
- gcc-8-tinyconfig - failed
* powerpc, build
- gcc-13-tinyconfig - failed
- gcc-8-tinyconfig - failed
Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
Build log:
--------
kernel/time/timekeeping.c: In function 'timekeeping_debug_get_ns':
kernel/time/timekeeping.c:286:1: error: no return statement in
function returning non-void [-Werror=return-type]
286 | }
| ^
cc1: some warnings being treated as errors
steps to reproduce:
---
# tuxmake --runtime podman --target-arch powerpc --toolchain gcc-13
--kconfig tinyconfig
Links:
- https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20240410/testrun/23380322/suite/build/test/gcc-13-tinyconfig/details/
- https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20240410/testrun/23380301/suite/build/test/gcc-11-tinyconfig/history/
- https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20240410/testrun/23380301/suite/build/tests/
--
Linaro LKFT
https://lkft.linaro.org
next reply other threads:[~2024-04-10 10:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-10 10:56 Naresh Kamboju [this message]
2024-04-10 13:03 ` tinyconfig: kernel/time/timekeeping.c:286:1: error: no return statement in function returning non-void [-Werror=return-type] Adrian Hunter
2024-04-10 15:35 ` Adrian Hunter
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+G9fYvjdZCW=7ZGxS6A_3bysjQ56YF7S-+PNLQ_8a4DKh1Bhg@mail.gmail.com' \
--to=naresh.kamboju@linaro.org \
--cc=adrian.hunter@intel.com \
--cc=anders.roxell@linaro.org \
--cc=arnd@arndb.de \
--cc=dan.carpenter@linaro.org \
--cc=jstultz@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=regressions@lists.linux.dev \
--cc=sboyd@kernel.org \
--cc=tglx@linutronix.de \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).