linux-kernel - Intend to work on the DRM_* logging macro conversion

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAHhBtNqB=jQTnY1eu8or=toczr93ehUeuBkAZ7axFPr4ZHPjCQ@mail.gmail.com>
Date: Mon, 16 Sep 2024 23:46:07 +0800
From: YJ Lin <0xff07@...il.com>
To: sean@...rly.run, rodrigosiqueiramelo@...il.com, mairacanal@...eup.net, 
	hamohammed.sa@...il.com, simona@...ll.ch, melissa.srw@...il.com, 
	maarten.lankhorst@...ux.intel.com, mripard@...nel.org, tzimmermann@...e.de, 
	airlied@...il.com, dri-devel@...ts.freedesktop.org, 
	linux-kernel@...r.kernel.org, YJ Lin <0xff07@...il.com>
Cc: ricardo@...liere.net, skhan@...uxfoundation.org, 
	Shuah Khan <shuah@...nel.org>
Subject: Intend to work on the DRM_* logging macro conversion

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!

(Also, do feel free to share tips for DRM and kernel development in general.)

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