From: Louis Chauvet <louis.chauvet@bootlin.com>
To: YJ Lin <0xff07@gmail.com>
Cc: sean@poorly.run, rodrigosiqueiramelo@gmail.com,
mairacanal@riseup.net, hamohammed.sa@gmail.com, simona@ffwll.ch,
melissa.srw@gmail.com, maarten.lankhorst@linux.intel.com,
mripard@kernel.org, tzimmermann@suse.de, airlied@gmail.com,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
ricardo@marliere.net, skhan@linuxfoundation.org,
Shuah Khan <shuah@kernel.org>
Subject: Re: Intend to work on the DRM_* logging macro conversion
Date: Wed, 18 Sep 2024 15:26:12 +0200 [thread overview]
Message-ID: <ZurU9K3SxwmQ3oJf@localhost.localdomain> (raw)
In-Reply-To: <CAHhBtNqB=jQTnY1eu8or=toczr93ehUeuBkAZ7axFPr4ZHPjCQ@mail.gmail.com>
Le 16/09/24 - 23:46, YJ Lin a écrit :
> Hi Sean and the vkms maintainers:
>
> I’m Leo, currently one of the mentees of the Linux Kernel Bug Fixing
> Program 2024 Summer Unpaid[1]. I saw an item on the DRM TODO list
> regarding "Convert logging to drm_* functions with drm_device
> parameter"[2]. It also suggests reaching out to the driver maintainers
> beforehand. So I’d like to understand your opinions toward making this
> conversion on the vkms driver, and I’d like to start working on it if
> you consider it suitable. Thank you!
Hi Leo,
It is very nice to work on this subject, thank you!
On the VKMS side, the current upstream driver can only create one instance
of the device, but we are working on supporting more, so it definitly
make sense to have per-device logging. Feel free to send patches to change
this where it make sense.
Few series are pending on the mailing list, so feel free to point where we
miss this too! (for example [3,4]
[3]:https://lore.kernel.org/all/20240912-google-vkms-managed-v3-0-7708d6ad262d@bootlin.com/
[4]:https://lore.kernel.org/all/20240912-b4-vkms-allocated-v1-0-29abbaa14af9@bootlin.com/
> (Also, do feel free to share tips for DRM and kernel development in general.)
Don't hesitate to send documentation patches if you had difficulties to
understand stuff, it will profit to everyone. If you need more
documentation about VKMS internals, a "big" patch is pending [5].
[5]:https://lore.kernel.org/all/20240905-google-clarifications-v4-1-e43c1f2e3d87@bootlin.com/
Thanks,
Louis Chauvet
> Best,
> Leo
>
> [1] https://mentorship.lfx.linuxfoundation.org/project/9c354ea7-f08e-4d85-a93d-94d2a3cb30c8
> [2] https://www.kernel.org/doc/html/latest/gpu/todo.html#convert-logging-to-drm-functions-with-drm-device-parameter
--
Louis Chauvet, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2024-09-18 13:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-16 15:46 YJ Lin
2024-09-18 13:26 ` Louis Chauvet [this message]
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=ZurU9K3SxwmQ3oJf@localhost.localdomain \
--to=louis.chauvet@bootlin.com \
--cc=0xff07@gmail.com \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=hamohammed.sa@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mairacanal@riseup.net \
--cc=melissa.srw@gmail.com \
--cc=mripard@kernel.org \
--cc=ricardo@marliere.net \
--cc=rodrigosiqueiramelo@gmail.com \
--cc=sean@poorly.run \
--cc=shuah@kernel.org \
--cc=simona@ffwll.ch \
--cc=skhan@linuxfoundation.org \
--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®