From: Koorosh Lahijani <kooroshlahijani@gmail.com>
To: "Sean Paul" <sean@poorly.run>,
"Alex Deucher" <alexander.deucher@amd.com>,
"Christian König" <christian.koenig@amd.com>
Cc: dri-devel@lists.freedesktop.org, amd-gfx@lists.freedesktop.org
Subject: Converting dev_* to drm_* in amdgpu
Date: Wed, 23 Jul 2025 00:11:25 +0300 [thread overview]
Message-ID: <87tt34aq2q.fsf@gmail.com> (raw)
Hi,
I'm Koorosh a computer engineering student, I like to start learning
kernel development and I'm interested in the Linux graphics stack.
I like to take up the task of converting the dev_* logging macros to
their drm_* counterparts if this change is wanted in amdgpu driver.
One small question about the task, it is mentioned in
linux/Documentation/gpu/todo.rst:217 that the reason for using dev_*
macros is differentiating between instances of the same driver, should I
do anything special on the format string part for this or leaving it to
the first argument of drm_* macros is enough?
Regards,
Koorosh
reply other threads:[~2025-07-22 21:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87tt34aq2q.fsf@gmail.com \
--to=kooroshlahijani@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=sean@poorly.run \
/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).