Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Javier Martinez Canillas <javierm@redhat.com>
To: Thomas Zimmermann <tzimmermann@suse.de>,
	mripard@kernel.org, maarten.lankhorst@linux.intel.com,
	daniel@ffwll.ch, airlied@gmail.com, suijingfeng@loongson.cn
Cc: laurent.pinchart@ideasonboard.com,
	dri-devel@lists.freedesktop.org, amd-gfx@lists.freedesktop.org,
	linux-renesas-soc@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	Thomas Zimmermann <tzimmermann@suse.de>
Subject: Re: [PATCH 5/8] drm/solomon: Do not include <drm/drm_plane_helper.h>
Date: Fri, 01 Dec 2023 09:42:31 +0100	[thread overview]
Message-ID: <871qc6mhzc.fsf@minerva.mail-host-address-is-not-set> (raw)
In-Reply-To: <20231128104723.20622-6-tzimmermann@suse.de>

Thomas Zimmermann <tzimmermann@suse.de> writes:

Hello Thomas,

> Remove unnecessary include statements for <drm/drm_plane_helper.h>.
> The file contains helpers for non-atomic code and should not be
> required by most drivers. No functional changes.
>
> Signed-off-by: Thomas Zimmermann <tzimmermann@suse.de>
> ---
>  drivers/gpu/drm/solomon/ssd130x.h | 1 -
>  1 file changed, 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/solomon/ssd130x.h b/drivers/gpu/drm/solomon/ssd130x.h
> index acf7cedf0c1ab..075c5c3ee75ac 100644
> --- a/drivers/gpu/drm/solomon/ssd130x.h
> +++ b/drivers/gpu/drm/solomon/ssd130x.h
> @@ -17,7 +17,6 @@
>  #include <drm/drm_crtc.h>
>  #include <drm/drm_drv.h>
>  #include <drm/drm_encoder.h>
> -#include <drm/drm_plane_helper.h>
>  
>  #include <linux/regmap.h>
>  
> -- 
> 2.43.0
>

Reviewed-by: Javier Martinez Canillas <javierm@redhat.com>

-- 
Best regards,

Javier Martinez Canillas
Core Platforms
Red Hat


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2023-12-01  8:43 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20231128104723.20622-1-tzimmermann@suse.de>
2023-11-28 10:45 ` [PATCH 1/8] drm/plane-helper: Move drm_plane_helper_atomic_check() into udl Thomas Zimmermann
2023-12-01  2:36   ` [1/8] " Sui Jingfeng
2023-12-01  8:22     ` Thomas Zimmermann
2023-12-01 13:57       ` Sui Jingfeng
2023-11-28 10:45 ` [PATCH 4/8] drm/shmobile: Do not include <drm/drm_plane_helper.h> Thomas Zimmermann
2023-11-28 13:16   ` Geert Uytterhoeven
2023-11-28 10:45 ` [PATCH 5/8] drm/solomon: " Thomas Zimmermann
2023-11-28 13:16   ` Geert Uytterhoeven
2023-12-01  8:42   ` Javier Martinez Canillas [this message]
2023-11-28 10:45 ` [PATCH 6/8] drm/ofdrm: " Thomas Zimmermann
2023-11-28 12:01   ` [6/8] " Sui Jingfeng
2023-11-28 10:45 ` [PATCH 7/8] drm/simpledrm: " Thomas Zimmermann
2023-11-28 11:47   ` [7/8] " Sui Jingfeng
2023-11-28 10:45 ` [PATCH 8/8] drm/xlnx: " Thomas Zimmermann
2023-11-28 11:02   ` Laurent Pinchart
2023-11-28 14:13     ` Thomas Zimmermann

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=871qc6mhzc.fsf@minerva.mail-host-address-is-not-set \
    --to=javierm@redhat.com \
    --cc=airlied@gmail.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=suijingfeng@loongson.cn \
    --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