All of lore.kernel.org
 help / color / mirror / Atom feed
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-riscv <linux-riscv@lists.infradead.org>,
	lkft-triage@lists.linaro.org,  regressions@lists.linux.dev
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Guo Ren <guoren@linux.alibaba.com>,  Guo Ren <guoren@kernel.org>,
	Palmer Dabbelt <palmer@rivosinc.com>,
	 Heiko Stuebner <heiko@sntech.de>, Arnd Bergmann <arnd@arndb.de>,
	 Paul Walmsley <paul.walmsley@sifive.com>,
	Albert Ou <aou@eecs.berkeley.edu>
Subject: [next] riscv: Linux next-20220404 riscv defconfig builds failed.
Date: Mon, 4 Apr 2022 15:28:41 +0530	[thread overview]
Message-ID: <CA+G9fYu_ZHOeOPDiwzXGL6Re8aFYW3K+JSL2Dozw=VHwaUFxyQ@mail.gmail.com> (raw)

Linux next-20220404 riscv defconfig builds failed.

Regressions found on riscv:
   - riscv-riscv-clang-14-defconfig
   - riscv-riscv-gcc-10-defconfig
   - riscv-riscv-clang-13-defconfig
   - riscv-riscv-clang-12-defconfig
   - riscv-riscv-clang-11-defconfig
   - riscv-riscv-gcc-11-defconfig
   - riscv-riscv-gcc-8-defconfig
   - riscv-riscv-gcc-9-defconfig
   - riscv-riscv-clang-nightly-defconfig


arch/riscv/kernel/compat_signal.c:7:10: fatal error:
linux/tracehook.h: No such file or directory
  7 | #include <linux/tracehook.h>
    |          ^~~~~~~~~~~~~~~~~~~
compilation terminated.
make[3]: *** [scripts/Makefile.build:289:
arch/riscv/kernel/compat_signal.o] Error 1


Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>

metadata:
    git_describe: next-20220404
    git_repo: https://gitlab.com/Linaro/lkft/mirrors/next/linux-next
    git_sha: 696206280c5e5c028caf9fd259999cb72b1f6127
    kconfig: defconfig
    target_arch: riscv
    toolchain: gcc-11

steps to reproduce:
  # To install tuxmake on your system globally:
  # sudo pip3 install -U tuxmake
  #

  tuxmake --runtime podman --target-arch riscv --toolchain gcc-11
--kconfig defconfig


--
Linaro LKFT
https://lkft.linaro.org


[1]  https://builds.tuxbuild.com/27JdBBUbSHIhFJ9Wsq3Z6ssitb6/

WARNING: multiple messages have this Message-ID (diff)
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-riscv <linux-riscv@lists.infradead.org>,
	lkft-triage@lists.linaro.org,  regressions@lists.linux.dev
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Guo Ren <guoren@linux.alibaba.com>, Guo Ren <guoren@kernel.org>,
	Palmer Dabbelt <palmer@rivosinc.com>,
	 Heiko Stuebner <heiko@sntech.de>, Arnd Bergmann <arnd@arndb.de>,
	 Paul Walmsley <paul.walmsley@sifive.com>,
	Albert Ou <aou@eecs.berkeley.edu>
Subject: [next] riscv: Linux next-20220404 riscv defconfig builds failed.
Date: Mon, 4 Apr 2022 15:28:41 +0530	[thread overview]
Message-ID: <CA+G9fYu_ZHOeOPDiwzXGL6Re8aFYW3K+JSL2Dozw=VHwaUFxyQ@mail.gmail.com> (raw)

Linux next-20220404 riscv defconfig builds failed.

Regressions found on riscv:
   - riscv-riscv-clang-14-defconfig
   - riscv-riscv-gcc-10-defconfig
   - riscv-riscv-clang-13-defconfig
   - riscv-riscv-clang-12-defconfig
   - riscv-riscv-clang-11-defconfig
   - riscv-riscv-gcc-11-defconfig
   - riscv-riscv-gcc-8-defconfig
   - riscv-riscv-gcc-9-defconfig
   - riscv-riscv-clang-nightly-defconfig


arch/riscv/kernel/compat_signal.c:7:10: fatal error:
linux/tracehook.h: No such file or directory
  7 | #include <linux/tracehook.h>
    |          ^~~~~~~~~~~~~~~~~~~
compilation terminated.
make[3]: *** [scripts/Makefile.build:289:
arch/riscv/kernel/compat_signal.o] Error 1


Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>

metadata:
    git_describe: next-20220404
    git_repo: https://gitlab.com/Linaro/lkft/mirrors/next/linux-next
    git_sha: 696206280c5e5c028caf9fd259999cb72b1f6127
    kconfig: defconfig
    target_arch: riscv
    toolchain: gcc-11

steps to reproduce:
  # To install tuxmake on your system globally:
  # sudo pip3 install -U tuxmake
  #

  tuxmake --runtime podman --target-arch riscv --toolchain gcc-11
--kconfig defconfig


--
Linaro LKFT
https://lkft.linaro.org


[1]  https://builds.tuxbuild.com/27JdBBUbSHIhFJ9Wsq3Z6ssitb6/

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

             reply	other threads:[~2022-04-04  9:58 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-04  9:58 Naresh Kamboju [this message]
2022-04-04  9:58 ` [next] riscv: Linux next-20220404 riscv defconfig builds failed Naresh Kamboju
2022-04-04 10:28 ` Guo Ren
2022-04-04 10:28   ` Guo Ren
2022-04-04 16:57 ` Nathan Chancellor
2022-04-04 16:57   ` Nathan Chancellor
2022-04-05  5:17   ` Guo Ren
2022-04-05  5:17     ` Guo Ren
2022-04-05 16:15     ` Palmer Dabbelt
2022-04-05 16:15       ` Palmer Dabbelt
2022-04-06  1:13       ` Guo Ren
2022-04-06  1:13         ` Guo Ren
2022-04-06  1:32         ` Guo Ren
2022-04-06  1:32           ` Guo Ren

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+G9fYu_ZHOeOPDiwzXGL6Re8aFYW3K+JSL2Dozw=VHwaUFxyQ@mail.gmail.com' \
    --to=naresh.kamboju@linaro.org \
    --cc=aou@eecs.berkeley.edu \
    --cc=arnd@arndb.de \
    --cc=guoren@kernel.org \
    --cc=guoren@linux.alibaba.com \
    --cc=heiko@sntech.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=lkft-triage@lists.linaro.org \
    --cc=palmer@rivosinc.com \
    --cc=paul.walmsley@sifive.com \
    --cc=regressions@lists.linux.dev \
    --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 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.