From: Jocelyn Falempe <jfalempe@redhat.com>
To: Thomas Zimmermann <tzimmermann@suse.de>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
Javier Martinez Canillas <javierm@redhat.com>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org
Cc: stable@vger.kernel.org
Subject: Re: [PATCH 0/6] drm/panic: Fixes found with kunit.
Date: Tue, 21 Oct 2025 14:32:14 +0200 [thread overview]
Message-ID: <2819877d-610f-42cf-9b3c-ee2d836e2df0@redhat.com> (raw)
In-Reply-To: <13bc66cd-a63b-44b9-92fb-98b5b36ce2dd@suse.de>
On 21/10/2025 13:24, Thomas Zimmermann wrote:
> Hi
>
> Am 21.10.25 um 11:35 schrieb Jocelyn Falempe:
>> On 09/10/2025 14:24, Jocelyn Falempe wrote:
>>> A few fixes for drm panic, that I found when writing unit tests with
>>> kunit.
>>
>> Pushed to drm-misc-fixes.
>
> There are many patches without Fixes tag here. Commits in -fixes should
> preferably have a Fixes tag to help with backporting. No need to revert,
> but something to keep in mind for next time.
Ok, sorry for that. I'll add it next time.
Best regards,
--
Jocelyn>
> Best regards
> Thomas
>
>>
>> Thanks Javier for your reviews.
>>
>>>
>>> Jocelyn Falempe (6):
>>> drm/panic: Fix drawing the logo on a small narrow screen
>>> drm/panic: Fix overlap between qr code and logo
>>> drm/panic: Fix qr_code, ensure vmargin is positive
>>> drm/panic: Fix kmsg text drawing rectangle
>>> drm/panic: Fix divide by 0 if the screen width < font width
>>> drm/panic: Fix 24bit pixel crossing page boundaries
>>>
>>> drivers/gpu/drm/drm_panic.c | 60 +++++++++++++++++++++++++++++++++----
>>> 1 file changed, 54 insertions(+), 6 deletions(-)
>>>
>>>
>>> base-commit: e4bea919584ff292c9156cf7d641a2ab3cbe27b0
>>
>
prev parent reply other threads:[~2025-10-21 12:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-09 12:24 [PATCH 0/6] drm/panic: Fixes found with kunit Jocelyn Falempe
2025-10-09 12:24 ` [PATCH 1/6] drm/panic: Fix drawing the logo on a small narrow screen Jocelyn Falempe
2025-10-14 7:32 ` Javier Martinez Canillas
2025-10-09 12:24 ` [PATCH 2/6] drm/panic: Fix overlap between qr code and logo Jocelyn Falempe
2025-10-09 12:31 ` kernel test robot
2025-10-14 7:32 ` Javier Martinez Canillas
2025-10-09 12:24 ` [PATCH 3/6] drm/panic: Fix qr_code, ensure vmargin is positive Jocelyn Falempe
2025-10-14 7:34 ` Javier Martinez Canillas
2025-10-09 12:24 ` [PATCH 4/6] drm/panic: Fix kmsg text drawing rectangle Jocelyn Falempe
2025-10-14 7:35 ` Javier Martinez Canillas
2025-10-09 12:24 ` [PATCH 5/6] drm/panic: Fix divide by 0 if the screen width < font width Jocelyn Falempe
2025-10-14 7:36 ` Javier Martinez Canillas
2025-10-09 12:24 ` [PATCH 6/6] drm/panic: Fix 24bit pixel crossing page boundaries Jocelyn Falempe
2025-10-14 7:37 ` Javier Martinez Canillas
2025-10-21 9:35 ` [PATCH 0/6] drm/panic: Fixes found with kunit Jocelyn Falempe
2025-10-21 11:24 ` Thomas Zimmermann
2025-10-21 12:32 ` Jocelyn Falempe [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=2819877d-610f-42cf-9b3c-ee2d836e2df0@redhat.com \
--to=jfalempe@redhat.com \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=javierm@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=simona@ffwll.ch \
--cc=stable@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).