public inbox for linux-clk@vger.kernel.org
 help / color / mirror / Atom feed
From: David Lechner <david@lechnology.com>
To: Stephen Boyd <sboyd@kernel.org>,
	Naresh Kamboju <naresh.kamboju@linaro.org>,
	linux-clk <linux-clk@vger.kernel.org>,
	clang-built-linux <llvm@lists.linux.dev>,
	open list <linux-kernel@vger.kernel.org>,
	lkft-triage@lists.linaro.org,
	Linux Regressions <regressions@lists.linux.dev>
Cc: hanchunchao@inspur.com,
	Michael Turquette <mturquette@baylibre.com>,
	Arnd Bergmann <arnd@arndb.de>,
	Dan Carpenter <dan.carpenter@linaro.org>,
	Anders Roxell <anders.roxell@linaro.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]
Date: Mon, 18 Nov 2024 08:28:21 -0600	[thread overview]
Message-ID: <2c7789dd-9583-4daa-918a-1bf14635f62e@lechnology.com> (raw)
In-Reply-To: <CA+G9fYs+gwu67Y0Tm2FHfNuUA5eLxT2FAWkfKvYrEbXJUXXiiA@mail.gmail.com>

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@linaro.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/

  reply	other threads:[~2024-11-18 14:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-18 13:10 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] Naresh Kamboju
2024-11-18 14:28 ` David Lechner [this message]
2024-11-19  3:46   ` Stephen Boyd

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=2c7789dd-9583-4daa-918a-1bf14635f62e@lechnology.com \
    --to=david@lechnology.com \
    --cc=anders.roxell@linaro.org \
    --cc=arnd@arndb.de \
    --cc=dan.carpenter@linaro.org \
    --cc=hanchunchao@inspur.com \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkft-triage@lists.linaro.org \
    --cc=llvm@lists.linux.dev \
    --cc=mturquette@baylibre.com \
    --cc=naresh.kamboju@linaro.org \
    --cc=regressions@lists.linux.dev \
    --cc=sboyd@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox