From: "Ricardo B. Marliere" <ricardo@marliere.net>
To: "Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Maxime Ripard" <mripard@kernel.org>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"David Airlie" <airlied@gmail.com>,
"Daniel Vetter" <daniel@ffwll.ch>,
"Hans de Goede" <hdegoede@redhat.com>,
"Helge Deller" <deller@gmx.de>,
"Sumit Semwal" <sumit.semwal@linaro.org>,
"Benjamin Gaignard" <benjamin.gaignard@collabora.com>,
"Brian Starkey" <Brian.Starkey@arm.com>,
"John Stultz" <jstultz@google.com>,
"T.J. Mercier" <tjmercier@google.com>,
"Christian König" <christian.koenig@amd.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
linux-fbdev@vger.kernel.org, linux-media@vger.kernel.org,
linaro-mm-sig@lists.linaro.org,
"Ricardo B. Marliere" <ricardo@marliere.net>
Subject: [PATCH RESEND drm-misc 0/4] drm: constify struct class usage
Date: Tue, 05 Mar 2024 08:34:09 -0300 [thread overview]
Message-ID: <20240305-class_cleanup-drm-v1-0-94f82740525a@marliere.net> (raw)
This is a simple and straight forward cleanup series that aims to make the
class structures in drm constant. This has been possible since 2023 [1].
[1]: https://lore.kernel.org/all/2023040248-customary-release-4aec@gregkh/
Signed-off-by: Ricardo B. Marliere <ricardo@marliere.net>
---
Ricardo B. Marliere (4):
drm/dp: make drm_dp_aux_dev_class constant
drm/sysfs: make drm_class constant
drm/fbdev/core: make fb_class constant
dma-buf: heaps: make dma_heap_class constant
drivers/dma-buf/dma-heap.c | 26 ++++++++++---------
drivers/gpu/drm/display/drm_dp_aux_dev.c | 22 ++++++++--------
drivers/gpu/drm/drm_internal.h | 2 +-
drivers/gpu/drm/drm_privacy_screen.c | 2 +-
drivers/gpu/drm/drm_sysfs.c | 44 ++++++++++++++------------------
drivers/video/fbdev/core/fb_internal.h | 2 +-
drivers/video/fbdev/core/fbcon.c | 4 +--
drivers/video/fbdev/core/fbmem.c | 17 ++++++------
drivers/video/fbdev/core/fbsysfs.c | 4 +--
9 files changed, 60 insertions(+), 63 deletions(-)
---
base-commit: 4a0e7b3c37531aabddf6f144b83ae9b65ec809fd
change-id: 20240305-class_cleanup-drm-591ca73b31f2
Best regards,
--
Ricardo B. Marliere <ricardo@marliere.net>
next reply other threads:[~2024-03-05 11:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-05 11:34 Ricardo B. Marliere [this message]
2024-03-05 11:34 ` [PATCH RESEND drm-misc 1/4] drm/dp: make drm_dp_aux_dev_class constant Ricardo B. Marliere
2024-03-05 11:34 ` [PATCH RESEND drm-misc 2/4] drm/sysfs: make drm_class constant Ricardo B. Marliere
2024-03-05 11:34 ` [PATCH RESEND drm-misc 3/4] drm/fbdev/core: make fb_class constant Ricardo B. Marliere
2024-03-05 11:34 ` [PATCH RESEND drm-misc 4/4] dma-buf: heaps: make dma_heap_class constant Ricardo B. Marliere
2024-03-05 17:07 ` T.J. Mercier
2024-03-05 18:02 ` Ricardo B. Marliere
2024-03-05 18:36 ` T.J. Mercier
2024-03-07 7:37 ` Sumit Semwal
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=20240305-class_cleanup-drm-v1-0-94f82740525a@marliere.net \
--to=ricardo@marliere.net \
--cc=Brian.Starkey@arm.com \
--cc=airlied@gmail.com \
--cc=benjamin.gaignard@collabora.com \
--cc=christian.koenig@amd.com \
--cc=daniel@ffwll.ch \
--cc=deller@gmx.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=hdegoede@redhat.com \
--cc=jstultz@google.com \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=sumit.semwal@linaro.org \
--cc=tjmercier@google.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).