From: yyaqia@gmail.com
To: Thomas Zimmermann <tzimmermann@suse.de>, deller@gmx.de, simona@ffwll.ch
Cc: dri-devel@lists.freedesktop.org, linux-fbdev@vger.kernel.org,
linux-kernel@vger.kernel.org, yaoyiqi3@huawei.com,
stable@vger.kernel.org
Subject: Re: [PATCH v3 2/3] fbcon: Rebuild rotated font buffer on font change
Date: Mon, 19 Oct 2026 16:46:37 +0800 [thread overview]
Message-ID: <atHdEJjrSTrlZtSU@blue> (raw)
In-Reply-To: <3382a02c-ed79-4214-99c5-dc81ee59d633@suse.de>
On 2026-10-16 09:59, Thomas Zimmermann wrote:
>
> It's way too long and boring to read. Can you please try to shorten the
> AI-generated commit description?
>
>
Sorry for that, I was a bit lazy to think commit desc by myself. I am
new to kernel and a little afraid that my message does not cover all
things.
> > - Also select the blitting type again in the error path of
> > fbcon_do_set_font(). On tile-blitting hardware, set_blitting_type()
> > uploads the font map to the text engine; without the second call, a
> > failed vc_resize() left the engine with the rejected font (found by
> > the Sashiko review).
>
> The problem is that rotate_font can fail as well. Handling that in the error
> path is not possible; hence results might be worse than keeping the rejected
> font. Can you try to keep the original rotated font and reinstall that
> directly?
>
Good advice, I will fix this in V4.
Thanks for your review,
Yao Yiqi
next prev parent reply other threads:[~2026-10-19 8:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-16 7:30 [PATCH v3 0/3] fbcon: fix rotated font buffer handling on font Yao Yiqi
2026-10-16 7:30 ` [PATCH v3 1/3] fbcon: Include font geometry in the rotated font cache Yao Yiqi
2026-10-18 14:05 ` Helge Deller
2026-10-19 9:12 ` yyaqia
2026-10-16 7:30 ` [PATCH v3 2/3] fbcon: Rebuild rotated font buffer on font change Yao Yiqi
2026-10-16 7:59 ` Thomas Zimmermann
2026-10-19 8:46 ` yyaqia [this message]
2026-10-16 7:30 ` [PATCH v3 3/3] fbcon: Retry rotated font allocation after failure Yao Yiqi
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=atHdEJjrSTrlZtSU@blue \
--to=yyaqia@gmail.com \
--cc=deller@gmx.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=simona@ffwll.ch \
--cc=stable@vger.kernel.org \
--cc=tzimmermann@suse.de \
--cc=yaoyiqi3@huawei.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
all inboxes | Powered by JetHome®