From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Maxime Ripard <maxime@cerno.tech>
Cc: David Airlie <airlied@linux.ie>,
Daniel Vetter <daniel.vetter@intel.com>,
Thomas Zimmermann <tzimmermann@suse.de>,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/sun4i: tv: Include drm_atomic.h
Date: Fri, 9 Sep 2022 12:39:01 +0300 [thread overview]
Message-ID: <YxsJtf6VRaNTqXUa@intel.com> (raw)
In-Reply-To: <20220909093116.4141982-1-maxime@cerno.tech>
On Fri, Sep 09, 2022 at 11:31:16AM +0200, Maxime Ripard wrote:
> Commit ec491291dc94 ("drm/sun4i: tv: Merge mode_set into atomic_enable")
> has introduced a call to drm_atomic_get_new_crtc_state(), but didn't
> include drm_atomic.h.
>
> On CONFIG_OF systems, this is fine because drm_atomic.h is included by
> drm_of.h through drm_bridge.h. However, whenever CONFIG_OF isn't set, we
> end up with a compilation error.
>
> Fixes: ec491291dc94 ("drm/sun4i: tv: Merge mode_set into atomic_enable")
> Reported-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> Signed-off-by: Maxime Ripard <maxime@cerno.tech>
Also caught by the robot since then:
https://lists.freedesktop.org/archives/dri-devel/2022-September/371257.html
Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> ---
> drivers/gpu/drm/sun4i/sun4i_tv.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/gpu/drm/sun4i/sun4i_tv.c b/drivers/gpu/drm/sun4i/sun4i_tv.c
> index 74ff5ad6a8b9..c65f0a89b6b0 100644
> --- a/drivers/gpu/drm/sun4i/sun4i_tv.c
> +++ b/drivers/gpu/drm/sun4i/sun4i_tv.c
> @@ -14,6 +14,7 @@
> #include <linux/regmap.h>
> #include <linux/reset.h>
>
> +#include <drm/drm_atomic.h>
> #include <drm/drm_atomic_helper.h>
> #include <drm/drm_of.h>
> #include <drm/drm_panel.h>
> --
> 2.37.1
--
Ville Syrjälä
Intel
next prev parent reply other threads:[~2022-09-09 9:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-09 9:31 [PATCH] drm/sun4i: tv: Include drm_atomic.h Maxime Ripard
2022-09-09 9:39 ` Ville Syrjälä [this message]
2022-09-09 9:43 ` (subset) " Maxime Ripard
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=YxsJtf6VRaNTqXUa@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=airlied@linux.ie \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=maxime@cerno.tech \
--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