From: Thomas Zimmermann <tzimmermann@suse.de>
To: Pierre Asselin <pa@panix.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
Javier Martinez Canillas <javierm@redhat.com>,
Hans de Goede <hdegoede@redhat.com>,
Ard Biesheuvel <ardb@kernel.org>
Subject: Re: [PATCH v3] firmware/sysfb: Fix VESA format selection
Date: Thu, 11 May 2023 10:05:54 +0200 [thread overview]
Message-ID: <b8f673e9-1a89-c3b6-7801-5f2d2d2f6c7b@suse.de> (raw)
In-Reply-To: <1f2a1e8ee99fc9f0a89ad47d112728c9.squirrel@mail.panix.com>
[-- Attachment #1.1: Type: text/plain, Size: 853 bytes --]
Hi
Am 10.05.23 um 19:25 schrieb Pierre Asselin:
> Thomas Zimmerman <tzimmermann@suse.de> writes:
>>
>> I found this casting mess even more unreadable. I went back to v2, fixed
>> the style issues and committed the patch as v4 (still under your name).
>>
>> https://cgit.freedesktop.org/drm/drm-tip/commit?id=1b617bc93178912fa36f87a957c15d1f1708c299
>
> Will this patch make it into Linux 6.4 ?
It appears to be stuck in the drm-misc-fixes tree. The time around the
merge window is always complicated. I've send out a reminder to the
maintainers to fetch the patch.
Best regards
Thomas
>
> --PA
>
--
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)
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
prev parent reply other threads:[~2023-05-11 8:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-20 15:57 [PATCH v3] firmware/sysfb: Fix VESA format selection Pierre Asselin
2023-04-20 16:05 ` Pierre Asselin
2023-04-21 11:32 ` Linux regression tracking (Thorsten Leemhuis)
2023-04-21 11:35 ` Thomas Zimmermann
2023-04-21 13:42 ` Pierre Asselin
2023-04-21 12:37 ` Thomas Zimmermann
2023-05-10 17:25 ` Pierre Asselin
2023-05-11 8:05 ` 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=b8f673e9-1a89-c3b6-7801-5f2d2d2f6c7b@suse.de \
--to=tzimmermann@suse.de \
--cc=ardb@kernel.org \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=hdegoede@redhat.com \
--cc=javierm@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pa@panix.com \
/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