[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2c7789dd-9583-4daa-918a-1bf14635f62e@lechnology.com>
Date: Mon, 18 Nov 2024 08:28:21 -0600
From: David Lechner <david@...hnology.com>
To: Stephen Boyd <sboyd@...nel.org>,
Naresh Kamboju <naresh.kamboju@...aro.org>,
linux-clk <linux-clk@...r.kernel.org>,
clang-built-linux <llvm@...ts.linux.dev>,
open list <linux-kernel@...r.kernel.org>, lkft-triage@...ts.linaro.org,
Linux Regressions <regressions@...ts.linux.dev>
Cc: hanchunchao@...pur.com, Michael Turquette <mturquette@...libre.com>,
Arnd Bergmann <arnd@...db.de>, Dan Carpenter <dan.carpenter@...aro.org>,
Anders Roxell <anders.roxell@...aro.org>
Subject: Re: drivers/clk/davinci/psc.c:281:10: error: incompatible integer to
pointer conversion returning 'int' from a function with result type 'struct
davinci_lpsc_clk *' [-Wint-conversion]
On 11/18/24 7:10 AM, Naresh Kamboju wrote:
> The davinci_all_defconfig and multi_v5_defconfig builds failed with clang-19 and
> clang-nightly on the Linux next-20241115 tag for the arm architectures.
> Same build pass with gcc-13.
>
> First seen on Linux next-20241118 tag.
> Good: next-20241115
> Bad: next-20241118
>
> arm
> * arm, build
> - clang-19-davinci_all_defconfig
> - clang-19-multi_v5_defconfig
> - clang-19-multi_v5_defconfig-65236a87
> - clang-nightly-davinci_all_defconfig
> - clang-nightly-multi_v5_defconfig
> - clang-nightly-multi_v5_defconfig-65236a87
>
> Reported-by: Linux Kernel Functional Testing <lkft@...aro.org>
>
> Build error:
> ---------
> drivers/clk/davinci/psc.c:281:10: error: incompatible integer to
> pointer conversion returning 'int' from a function with result type
> 'struct davinci_lpsc_clk *' [-Wint-conversion]
> 281 | return -ENOMEM;
> | ^~~~~~~
> 1 error generated.
> make[6]: *** [scripts/Makefile.build:200: drivers/clk/davinci/psc.o] Error 1
>
> Build image:
> -----------
> - https://storage.tuxsuite.com/public/linaro/lkft/builds/2p15j4StPnjuuRXu3qgndSTbahH/
> - https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20241118/testrun/25881399/suite/build/test/clang-19-davinci_all_defconfig/history/
> - https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20241118/testrun/25881399/suite/build/test/clang-19-davinci_all_defconfig/details/
> - https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20241118/testrun/25881399/suite/build/test/clang-19-davinci_all_defconfig/log
>
> Steps to reproduce:
> ------------
> - # tuxmake --runtime podman --target-arch arm --toolchain clang-19
> --kconfig davinci_all_defconfig LLVM=1 LLVM_IAS=1
>
> metadata:
> ----
> git describe: next-20241118
> git repo: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> git sha: ae58226b89ac0cffa05ba7357733776542e40216
> kernel config:
> https://storage.tuxsuite.com/public/linaro/lkft/builds/2p15j4StPnjuuRXu3qgndSTbahH/config
> build url: https://storage.tuxsuite.com/public/linaro/lkft/builds/2p15j4StPnjuuRXu3qgndSTbahH/
> toolchain: clang-19
> config: davinci_all_defconfig and multi_v5_defconfig
> arch: arm
>
> --
> Linaro LKFT
> https://lkft.linaro.org
Hi Stephen,
This is caused by [1]. I looked at it again and the patch is wrong.
Can you drop it from your tree or should we send another patch to
fix the bad patch?
[1]: https://lore.kernel.org/linux-clk/20241114091422.75412-1-hanchunchao@inspur.com/
Powered by blists - more mailing lists