From: Greg KH <gregkh@linuxfoundation.org>
To: Zsolt Kajtar <soci@c64.rulez.org>
Cc: linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org,
jirislaby@kernel.org
Subject: Re: [PATCH v2 0/4] tty/vt: fix various 512 glyph font issues
Date: Sat, 6 Sep 2025 13:42:05 +0200 [thread overview]
Message-ID: <2025090650-support-emergency-3599@gregkh> (raw)
In-Reply-To: <20250901052636.8981-1-soci@c64.rulez.org>
On Mon, Sep 01, 2025 at 07:26:32AM +0200, Zsolt Kajtar wrote:
> Having the 8th bit of a glyph in the attribute byte is tricky business.
> These patches fix most of the cases where it went wrong in the VT code.
> What remains is related to fbcon as well and so not part of this series.
>
> This run fixes concerns raised on review and adds one more patch for a
> problem which doesn't cause visible effects.
>
> These patches were prepared to apply on tty-next.
>
> Zsolt Kajtar (4):
> tty/vt: 8th bit location in vc_uniscr routines
> tty/vt: Prevent 8th bit corruption with soft cursor
> tty/vt: Fix unreadable kernel messages on vgacon
> tty/vt: use correct attribute mask in do_update_region
>
> drivers/tty/vt/vt.c | 40 ++++++++++++++++++++++++++--------------
> 1 file changed, 26 insertions(+), 14 deletions(-)
>
> --
> 2.30.2
>
>
Hi,
This is the friendly patch-bot of Greg Kroah-Hartman. You have sent him
a patch that has triggered this response. He used to manually respond
to these common problems, but in order to save his sanity (he kept
writing the same thing over and over, yet to different people), I was
created. Hopefully you will not take offence and will fix the problem
in your patch and resubmit it so that it can be accepted into the Linux
kernel tree.
You are receiving this message because of the following common error(s)
as indicated below:
- This looks like a new version of a previously submitted patch, but you
did not list below the --- line any changes from the previous version.
Please read the section entitled "The canonical patch format" in the
kernel file, Documentation/process/submitting-patches.rst for what
needs to be done here to properly describe this.
If you wish to discuss this problem further, or you have questions about
how to resolve this issue, please feel free to respond to this email and
Greg will reply once he has dug out from the pending patches received
from other developers.
thanks,
greg k-h's patch email bot
prev parent reply other threads:[~2025-09-06 11:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-01 5:26 [PATCH v2 0/4] tty/vt: fix various 512 glyph font issues Zsolt Kajtar
2025-09-01 5:26 ` [PATCH v2 1/4] tty/vt: 8th bit location in vc_uniscr routines Zsolt Kajtar
2025-09-01 5:26 ` [PATCH v2 2/4] tty/vt: Prevent 8th bit corruption with soft cursor Zsolt Kajtar
2025-09-01 5:26 ` [PATCH v2 3/4] tty/vt: Fix unreadable kernel messages on vgacon Zsolt Kajtar
2025-09-01 5:26 ` [PATCH v2 4/4] tty/vt: use correct attribute mask in do_update_region Zsolt Kajtar
2025-09-06 11:42 ` Greg KH [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=2025090650-support-emergency-3599@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=soci@c64.rulez.org \
/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).