From: Eslam Khafagy <eslam.medhat1993@gmail.com>
Cc: skhan@linuxfoundation.com,
Eslam Khafagy <eslam.medhat1993@gmail.com>,
Manikandan Muralidharan <manikandan.m@microchip.com>,
Dharma Balasubiramani <dharma.b@microchip.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
Nicolas Ferre <nicolas.ferre@microchip.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Claudiu Beznea <claudiu.beznea@tuxon.dev>,
dri-devel@lists.freedesktop.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/1] drm: atmel-hlcdc: replace dev_* print funtions with drm_*
Date: Wed, 6 Aug 2025 02:56:50 +0300 [thread overview]
Message-ID: <20250805235928.236248-1-eslam.medhat1993@gmail.com> (raw)
Hi, this patch is to replace dev_* print function for the atmel_hlcdc
driver with more prefered drm_* variant [1].
It's eventualy up to you the mainterner to chose to apply this patch.
but since i am a starter to the kernel i'd appreciate it if you do.
[1] https://docs.kernel.org/gpu/todo.html#convert-logging-to-drm-functions-with-drm-device-parameter
Eslam Khafagy (1):
drm: atmel-hlcdc: replace dev_* print funtions with drm_* variants
.../gpu/drm/atmel-hlcdc/atmel_hlcdc_crtc.c | 20 +++++++++----------
drivers/gpu/drm/atmel-hlcdc/atmel_hlcdc_dc.c | 14 ++++++-------
.../gpu/drm/atmel-hlcdc/atmel_hlcdc_output.c | 2 +-
.../gpu/drm/atmel-hlcdc/atmel_hlcdc_plane.c | 2 +-
4 files changed, 19 insertions(+), 19 deletions(-)
--
2.43.0
next reply other threads:[~2025-08-05 23:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-05 23:56 Eslam Khafagy [this message]
2025-08-06 0:01 ` [PATCH 1/1] drm: atmel-hlcdc: replace dev_* print funtions with drm_* variants Eslam Khafagy
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=20250805235928.236248-1-eslam.medhat1993@gmail.com \
--to=eslam.medhat1993@gmail.com \
--cc=airlied@gmail.com \
--cc=alexandre.belloni@bootlin.com \
--cc=claudiu.beznea@tuxon.dev \
--cc=dharma.b@microchip.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=manikandan.m@microchip.com \
--cc=mripard@kernel.org \
--cc=nicolas.ferre@microchip.com \
--cc=simona@ffwll.ch \
--cc=skhan@linuxfoundation.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
all inboxes | Powered by JetHome®