From: linux@treblig.org
To: dmitry.baryshkov@linaro.org, ville.syrjala@linux.intel.com,
jfalempe@redhat.com, tomi.valkeinen@ideasonboard.com,
maarten.lankhorst@linux.intel.com, mripard@kernel.org,
tzimmermann@suse.de, airlied@gmail.com, simona@ffwll.ch
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
"Dr. David Alan Gilbert" <linux@treblig.org>
Subject: [PATCH v2 0/3] DRM deadcode
Date: Tue, 29 Oct 2024 23:47:02 +0000 [thread overview]
Message-ID: <20241029234706.285087-1-linux@treblig.org> (raw)
From: "Dr. David Alan Gilbert" <linux@treblig.org>
This is a bunch of deadcode removals; the first two are
strictly whole function removals; the last as a revert
also undoes an extra parameter that was added. It was a clean
revert.
v2
Drop Remove unused drm_client_framebuffer_flush
Jocelyn & Thomas have plans for it
Drop Remove unused drm_crtc_vblank_count_and_time
Ville thinks it might be easy to make use of
Convert Remove unused drm_client_modeset_check
As suggested by Dmitry, make this a full revert
Dr. David Alan Gilbert (3):
drm: Remove unused drm_atomic_helper_commit_planes_on_crtc
drm/sysfs: Remove unused drm_class_device_(un)register
Revert "drm/client: Add drm_client_modeset_check()"
drivers/gpu/drm/drm_atomic_helper.c | 72 ----------------------------
drivers/gpu/drm/drm_client_modeset.c | 35 ++------------
drivers/gpu/drm/drm_sysfs.c | 32 -------------
include/drm/drm_atomic_helper.h | 1 -
include/drm/drm_client.h | 1 -
include/drm/drm_sysfs.h | 4 --
6 files changed, 4 insertions(+), 141 deletions(-)
--
2.47.0
next reply other threads:[~2024-10-29 23:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-29 23:47 linux [this message]
2024-10-29 23:47 ` [PATCH v2 1/3] drm: Remove unused drm_atomic_helper_commit_planes_on_crtc linux
2024-10-29 23:47 ` [PATCH v2 2/3] drm/sysfs: Remove unused drm_class_device_(un)register linux
2024-10-29 23:47 ` [PATCH v2 3/3] Revert "drm/client: Add drm_client_modeset_check()" linux
2024-10-31 21:47 ` Dmitry Baryshkov
2025-01-31 12:56 ` Dr. David Alan Gilbert
2025-03-03 16:58 ` Dr. David Alan Gilbert
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=20241029234706.285087-1-linux@treblig.org \
--to=linux@treblig.org \
--cc=airlied@gmail.com \
--cc=dmitry.baryshkov@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jfalempe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=simona@ffwll.ch \
--cc=tomi.valkeinen@ideasonboard.com \
--cc=tzimmermann@suse.de \
--cc=ville.syrjala@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