From: Thomas Zimmermann <tzimmermann@suse.de>
To: Leander Kieweg <kieweg.leander@gmail.com>,
Gerd Hoffmann <kraxel@redhat.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>
Cc: David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
dri-devel@lists.freedesktop.org, virtualization@lists.linux.dev,
Sean Paul <seanpaul@chromium.org>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC] Plan to convert drm/tiny/bochs to drm_* logging
Date: Mon, 18 Aug 2025 08:57:05 +0200 [thread overview]
Message-ID: <dd2d2d3e-10be-47bf-9a71-3bec58067688@suse.de> (raw)
In-Reply-To: <20250817235836.134286-1-kieweg.leander@gmail.com>
Hi
Am 18.08.25 um 01:57 schrieb Leander Kieweg:
> From: [Leander Kieweg] <kieweg.leander@gmail.com>
>
> Hello,
>
> I am a new contributor looking to get started with kernel development. I found the "Convert logging to drm_* functions" task on the gpu/todo.html list.
> The task description advises contacting the relevant maintainers before starting the work to ensure a patch would be welcome.
> After setting up a build and test environment, I've identified the drm/tiny/bochs driver as a good, self-contained candidate for this conversion.
> Would a patch to convert the remaining legacy logging calls in this driver to their modern drm_* equivalents be welcome?
I've not looked into the driver what's left to do, but sure, go ahead.
Best regards
Thomas
> Thank you for your time,
>
> Leander Kieweg
--
--
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Frankenstrasse 146, 90461 Nuernberg, Germany
GF: Ivo Totev, Andrew Myers, Andrew McDonald, Boudien Moerman
HRB 36809 (AG Nuernberg)
prev parent reply other threads:[~2025-08-18 6:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-17 23:57 Leander Kieweg
2025-08-18 6:57 ` Thomas Zimmermann [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=dd2d2d3e-10be-47bf-9a71-3bec58067688@suse.de \
--to=tzimmermann@suse.de \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=kieweg.leander@gmail.com \
--cc=kraxel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=seanpaul@chromium.org \
--cc=simona@ffwll.ch \
--cc=virtualization@lists.linux.dev \
/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®