mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Min-Hua Chen <minhuadotchen@gmail.com>
To: didi.debian@cknow.org
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, minhuadotchen@gmail.com,
	mripard@kernel.org, tzimmermann@suse.de
Subject: Re: [PATCH] drm/rockchip: include rockchip_drm_drv.h
Date: Sat,  7 Sep 2024 11:02:59 +0800	[thread overview]
Message-ID: <20240907030259.1243487-1-minhuadotchen@gmail.com> (raw)
In-Reply-To: <D3Z5JMTKPQIS.2M5O5DY0S4U9G@cknow.org>

>FWIW: I didn't see it either, but I assumed I was missing the right
>context (i.e. patches) needed to trigger that warning.
>
FYI

I triggered the warning by the following step:

install 'sparse' first

git clone https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
cd linux
ARCH=arm64 LLVM=1 make C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' mrproper defconfig all -j8


cheers,
Min-Hua

>
>> While implementing my feature, I happened to find that I need to
>> include rockchip_drm_drv.h in rockchip_drm_vop2.h
>
>Makes perfect sense :)
>But if the warning is indeed valid, it should be fixed on its own (IMO).
>
>Cheers,
>  Diederik


  reply	other threads:[~2024-09-07  3:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-05 22:38 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 [this message]
2024-09-07  8:47           ` Diederik de Haas
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=20240907030259.1243487-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
all inboxes | Powered by JetHome®