From: Naresh Kamboju <naresh.kamboju@linaro.org>
To: Linux-Next Mailing List <linux-next@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>,
lkft-triage@lists.linaro.org
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Andrew Morton <akpm@linux-foundation.org>,
Peter Xu <peterx@redhat.com>,
Alistair Popple <apopple@nvidia.com>,
Andrea Arcangeli <aarcange@redhat.com>,
Axel Rasmussen <axelrasmussen@google.com>,
David Hildenbrand <david@redhat.com>,
Hugh Dickins <hughd@google.com>,
Jerome Glisse <jglisse@redhat.com>,
"Kirill A . Shutemov" <kirill@shutemov.name>,
Matthew Wilcox <willy@infradead.org>,
Mike Kravetz <mike.kravetz@oracle.com>,
Mike Rapoport <rppt@linux.vnet.ibm.com>,
Nadav Amit <nadav.amit@gmail.com>, Arnd Bergmann <arnd@arndb.de>
Subject: [next] sh: hugetlb.h:27:1: error: no return statement in function returning non-void [-Werror=return-type]
Date: Wed, 11 May 2022 21:26:45 +0530 [thread overview]
Message-ID: <CA+G9fYtS5fXzbODO3+Rz7VE4VvjY_1c99Da5UhruXi16jcVGbw@mail.gmail.com> (raw)
Following build regressions were noticed on sh builds on linux next-20220511
with gcc-11, gcc-10, gcc-9 and gcc-8.
Regressions found on sh:
- gcc-11-microdev_defconfig
- gcc-11-shx3_defconfig
- gcc-8-defconfig
- gcc-9-shx3_defconfig
- gcc-8-dreamcast_defconfig
- gcc-10-defconfig
- gcc-10-microdev_defconfig
- gcc-8-shx3_defconfig
- gcc-8-microdev_defconfig
- gcc-11-dreamcast_defconfig
- gcc-9-microdev_defconfig
- gcc-10-dreamcast_defconfig
- gcc-11-defconfig
- gcc-10-shx3_defconfig
- gcc-9-defconfig
- gcc-9-dreamcast_defconfig
Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
In file included from include/linux/hugetlb.h:757,
from mm/filemap.c:36:
arch/sh/include/asm/hugetlb.h: In function 'huge_ptep_clear_flush':
arch/sh/include/asm/hugetlb.h:27:1: error: no return statement in
function returning non-void [-Werror=return-type]
27 | }
| ^
cc1: some warnings being treated as errors
make[2]: *** [scripts/Makefile.build:295: mm/filemap.o] Error 1
Build url: https://builds.tuxbuild.com/291BWxg5eELaKSwUXNLIqh5w1k3/
--
Linaro LKFT
https://lkft.linaro.org
next reply other threads:[~2022-05-11 15:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-11 15:56 Naresh Kamboju [this message]
2022-05-11 18:37 ` [next] sh: hugetlb.h:27:1: error: no return statement in function returning non-void [-Werror=return-type] Matthew Wilcox
2022-05-12 0:15 ` Baolin Wang
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+G9fYtS5fXzbODO3+Rz7VE4VvjY_1c99Da5UhruXi16jcVGbw@mail.gmail.com \
--to=naresh.kamboju@linaro.org \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=apopple@nvidia.com \
--cc=arnd@arndb.de \
--cc=axelrasmussen@google.com \
--cc=david@redhat.com \
--cc=hughd@google.com \
--cc=jglisse@redhat.com \
--cc=kirill@shutemov.name \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=mike.kravetz@oracle.com \
--cc=nadav.amit@gmail.com \
--cc=peterx@redhat.com \
--cc=rppt@linux.vnet.ibm.com \
--cc=sfr@canb.auug.org.au \
--cc=willy@infradead.org \
/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.