linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Baolin Wang <baolin.wang@linux.alibaba.com>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Andrew Morton <akpm@linux-foundation.org>,
	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
Subject: Re: [next] sh: hugetlb.h:27:1: error: no return statement in function returning non-void [-Werror=return-type]
Date: Thu, 12 May 2022 08:15:55 +0800	[thread overview]
Message-ID: <b04fb722-1a35-9586-93e2-b9353e2944d7@linux.alibaba.com> (raw)
In-Reply-To: <CA+G9fYtS5fXzbODO3+Rz7VE4VvjY_1c99Da5UhruXi16jcVGbw@mail.gmail.com>

Hi,

On 5/11/2022 11:56 PM, Naresh Kamboju wrote:
> 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/

Thanks for reporting. I'm sorry for my stupid mistakes. I've sent out a 
V4 to fix building issues[1], and Stephen will update today's 
(next-20220512) linux-next. Please test today's linux-next. Sorry for 
troubles again.

[1] 
https://lore.kernel.org/all/cover.1652270205.git.baolin.wang@linux.alibaba.com/

      parent reply	other threads:[~2022-05-12  0:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-11 15:56 [next] sh: hugetlb.h:27:1: error: no return statement in function returning non-void [-Werror=return-type] Naresh Kamboju
2022-05-11 18:37 ` Matthew Wilcox
2022-05-12  0:15 ` Baolin Wang [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=b04fb722-1a35-9586-93e2-b9353e2944d7@linux.alibaba.com \
    --to=baolin.wang@linux.alibaba.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-next@vger.kernel.org \
    --cc=lkft-triage@lists.linaro.org \
    --cc=naresh.kamboju@linaro.org \
    --cc=sfr@canb.auug.org.au \
    /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 NNTP newsgroup(s).