From: Heiko Stuebner <heiko@sntech•de>
To: Ben Dooks <ben.dooks@codethink•co.uk>
Cc: linux-kernel@lists•codethink.co.uk,
David Airlie <airlied@linux•ie>, Sandy Huang <hjc@rock-chips•com>,
dri-devel@lists•freedesktop.org, linux-kernel@vger•kernel.org,
linux-rockchip@lists•infradead.org,
Daniel Vetter <daniel@ffwll•ch>,
linux-arm-kernel@lists•infradead.org
Subject: Re: [PATCH] drm/rockchip: include rockchip_drm_drv.h
Date: Sun, 13 Oct 2019 23:57:36 +0200 [thread overview]
Message-ID: <12674451.zEyZYcXUJe@phil> (raw)
In-Reply-To: <20191009132134.18384-1-ben.dooks@codethink.co.uk>
Am Mittwoch, 9. Oktober 2019, 15:21:34 CEST schrieb Ben Dooks:
> Include rockchip_drm_drv.h for definition of vop_platform_driver
> to avoid the following sparse warning:
>
> drivers/gpu/drm/rockchip/rockchip_vop_reg.c:982:24: warning: symbol 'vop_platform_driver' was not declared. Should it be static?
>
> Signed-off-by: Ben Dooks <ben.dooks@codethink•co.uk>
applied to drm-misc-next
Thanks
Heiko
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists•infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-10-13 21:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-09 13:21 [PATCH] drm/rockchip: include rockchip_drm_drv.h Ben Dooks
2019-10-13 21:57 ` Heiko Stuebner [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-09-05 22:38 Min-Hua Chen
2024-09-06 0:42 ` Andy Yan
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
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=12674451.zEyZYcXUJe@phil \
--to=heiko@sntech$(echo .)de \
--cc=airlied@linux$(echo .)ie \
--cc=ben.dooks@codethink$(echo .)co.uk \
--cc=daniel@ffwll$(echo .)ch \
--cc=dri-devel@lists$(echo .)freedesktop.org \
--cc=hjc@rock-chips$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-kernel@lists$(echo .)codethink.co.uk \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-rockchip@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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