From: Thomas Zimmermann <tzimmermann@suse.de>
To: airlied@linux.ie, daniel@ffwll.ch,
maarten.lankhorst@linux.intel.com, mripard@kernel.org,
alexander.deucher@amd.com, christian.koenig@amd.com,
sakari.ailus@linux.intel.com
Cc: Thomas Zimmermann <tzimmermann@suse.de>,
dri-devel@lists.freedesktop.org, amd-gfx@lists.freedesktop.org
Subject: [PATCH 0/4] drm: Finally retire struct drm_format_name_buf
Date: Sun, 16 May 2021 14:13:11 +0200 [thread overview]
Message-ID: <20210516121315.30321-1-tzimmermann@suse.de> (raw)
This is a cleanup patchset to remove drm_format_name_buf et al. There
are two instances in drivers that need to be replaced with the %4cc
printk format modifier. Patch 3 was left over back from an earlier
patchset. [1] Patch 4 removes struct drm_format_name_buf.
I built-tested with drm-tip. The patchsetcan be mered through drm-misc.
[1] https://lore.kernel.org/dri-devel/20210216155723.17109-1-sakari.ailus@linux.intel.com/
Sakari Ailus (1):
drm: Remove drm_get_format_name()
Thomas Zimmermann (3):
drm/amdgpu: Use %p4cc to print 4CC format
drm/simpledrm: Use %p4cc to print 4CC format
drm/fourcc: Remove struct drm_format_buf_name
drivers/gpu/drm/amd/amdgpu/amdgpu_display.c | 7 ++----
drivers/gpu/drm/drm_fourcc.c | 25 ---------------------
drivers/gpu/drm/tiny/simpledrm.c | 6 ++---
include/drm/drm_fourcc.h | 9 --------
4 files changed, 4 insertions(+), 43 deletions(-)
--
2.31.1
next reply other threads:[~2021-05-16 12:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-16 12:13 Thomas Zimmermann [this message]
2021-05-16 12:13 ` [PATCH 1/4] drm/amdgpu: Use %p4cc to print 4CC format Thomas Zimmermann
2021-05-16 12:24 ` Christian König
2021-05-16 12:13 ` [PATCH 2/4] drm/simpledrm: " Thomas Zimmermann
2021-05-16 12:13 ` [PATCH 3/4] drm: Remove drm_get_format_name() Thomas Zimmermann
2021-05-16 12:13 ` [PATCH 4/4] drm/fourcc: Remove struct drm_format_buf_name Thomas Zimmermann
2021-05-26 19:21 ` [PATCH 0/4] drm: Finally retire struct drm_format_name_buf Thomas Zimmermann
2021-05-26 19:54 ` Sakari Ailus
2021-05-27 2:32 ` Alex Deucher
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=20210516121315.30321-1-tzimmermann@suse.de \
--to=tzimmermann@suse.de \
--cc=airlied@linux.ie \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=sakari.ailus@linux.intel.com \
/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).