From: "Diederik de Haas" <didi.debian@cknow.org>
To: "Min-Hua Chen" <minhuadotchen@gmail.com>
Cc: <airlied@gmail.com>, <andy.yan@rock-chips.com>,
<andyshrk@163.com>, <daniel@ffwll.ch>,
<dri-devel@lists.freedesktop.org>, <heiko@sntech.de>,
<hjc@rock-chips.com>, <linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
<linux-rockchip@lists.infradead.org>,
<maarten.lankhorst@linux.intel.com>, <mripard@kernel.org>,
<tzimmermann@suse.de>
Subject: Re: [PATCH] drm/rockchip: include rockchip_drm_drv.h
Date: Sat, 07 Sep 2024 10:47:18 +0200 [thread overview]
Message-ID: <D3ZX6LZNLOYC.30CT6AX32VI2T@cknow.org> (raw)
In-Reply-To: <20240907030259.1243487-1-minhuadotchen@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1959 bytes --]
On Sat Sep 7, 2024 at 5:02 AM CEST, Min-Hua Chen wrote:
> >FWIW: I didn't see it either, but I assumed I was missing the right
> >context (i.e. patches) needed to trigger that warning.
>
> I triggered the warning by the following step:
>
> install 'sparse' first
>
> ARCH=arm64 LLVM=1 make C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' mrproper defconfig all -j8
This, especially the 'LLVM' part, is important context information
and should be part of the commit message.
I had only just started when I saw a number of sparse warnings:
DTC arch/arm64/boot/dts/rockchip/rk3588-edgeble-neu6a-io.dtb
OVL arch/arm64/boot/dts/ti/k3-j721e-evm.dtb
OVL arch/arm64/boot/dts/ti/k3-j721s2-evm.dtb
OVL arch/arm64/boot/dts/ti/k3-am654-idk.dtb
DTC arch/arm64/boot/dts/qcom/sc7180-trogdor-lazor-r3-kb.dtb
DTC arch/arm64/boot/dts/rockchip/rk3588-edgeble-neu6a-wifi.dtbo
DTC arch/arm64/boot/dts/qcom/sc7180-trogdor-lazor-r3-lte.dtb
DTC arch/arm64/boot/dts/rockchip/rk3588-edgeble-neu6b-io.dtb
DTC arch/arm64/boot/dts/rockchip/rk3588-evb1-v10.dtb
DTC arch/arm64/boot/dts/qcom/sc7180-trogdor-lazor-r9.dtb
../init/main.c:192:12: sparse: warning: symbol 'envp_init' was not declared. Should it be static?
../init/main.c:290:16: sparse: warning: cast to restricted __le32
../init/main.c:291:16: sparse: warning: cast to restricted __le32
CHECK ../init/do_mounts.c
And several followed, including in c-code files. So I stopped the build
and assume you've identified a or several actual issues.
I've seen several commits where changes were made because LLVM flagged
potentially problematic code, where GCC did not, so it's quite possible
you're on to something here.
But it would be helpful if the commit message said what code was
potentially problematic and why. And then the proper fix for that could
indeed be to include `rockchip_drm_drv.h`.
Cheers,
Diederik
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2024-09-07 8:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-05 22:38 [PATCH] drm/rockchip: include rockchip_drm_drv.h Min-Hua Chen
2024-09-06 0:42 ` Andy Yan
2024-09-06 9:17 ` Min-Hua Chen
2024-09-06 9:28 ` [PATCH] " Diederik de Haas
2024-09-06 9:50 ` Andy Yan
2024-09-06 11:07 ` Diederik de Haas
2024-09-07 3:02 ` Min-Hua Chen
2024-09-07 8:47 ` Diederik de Haas [this message]
2024-09-07 8:56 ` Andy Yan
2024-09-08 13:12 ` Min-Hua Chen
-- strict thread matches above, loose matches on Subject: below --
2019-10-09 13:21 Ben Dooks
2019-10-13 21:57 ` Heiko Stuebner
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=D3ZX6LZNLOYC.30CT6AX32VI2T@cknow.org \
--to=didi.debian@cknow.org \
--cc=airlied@gmail.com \
--cc=andy.yan@rock-chips.com \
--cc=andyshrk@163.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=heiko@sntech.de \
--cc=hjc@rock-chips.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=minhuadotchen@gmail.com \
--cc=mripard@kernel.org \
--cc=tzimmermann@suse.de \
/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