From: Min-Hua Chen <minhuadotchen@gmail.com>
To: andyshrk@163.com
Cc: airlied@gmail.com, andy.yan@rock-chips.com, daniel@ffwll.ch,
didi.debian@cknow.org, 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, minhuadotchen@gmail.com,
mripard@kernel.org, tzimmermann@suse.de
Subject: Re:Re: [PATCH] drm/rockchip: include rockchip_drm_drv.h
Date: Sun, 8 Sep 2024 21:12:37 +0800 [thread overview]
Message-ID: <20240908131237.741-1-minhuadotchen@gmail.com> (raw)
In-Reply-To: <175266d5.2a89.191cbb2a62e.Coremail.andyshrk@163.com>
>> 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
>
>>
>
>
>I can see same warnings, a lots of。
>And also see the warning in vop2:
>drivers/gpu/drm/rockchip/rockchip_vop2_reg.c:502:24: sparse: warning: symbol 'vop2_platform_driver' was not declared. Should it be static?
>
>
>Min Hua,If you are agree,I will split it from my patch, and add a Fix tag ,and also add a SoB of you, Then resend in My V3 series,this
>will make my patch series easier。
It looks good to me. Thank you and Diederik for commenting.
cheers,
Min-Hua
> >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
prev parent reply other threads:[~2024-09-08 13:14 UTC|newest]
Thread overview: 10+ 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
2024-09-07 8:56 ` Andy Yan
2024-09-08 13:12 ` Min-Hua Chen [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=20240908131237.741-1-minhuadotchen@gmail.com \
--to=minhuadotchen@gmail.com \
--cc=airlied@gmail.com \
--cc=andy.yan@rock-chips.com \
--cc=andyshrk@163.com \
--cc=daniel@ffwll.ch \
--cc=didi.debian@cknow.org \
--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=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;
as well as URLs for NNTP newsgroup(s).