From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: qemu-devel@nongnu.org,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
qemu-stable <qemu-stable@nongnu.org>
Subject: Re: [PATCH v2 0/3] ui/vnc: fix some endian problems
Date: Fri, 30 May 2025 11:13:26 +0100 [thread overview]
Message-ID: <aDmExrPVuuwSfZHA@redhat.com> (raw)
In-Reply-To: <3371b5fc-80ad-4873-b914-21e8af9690fe@tls.msk.ru>
On Sat, May 24, 2025 at 01:32:45PM +0300, Michael Tokarev wrote:
> On 14.05.2025 14:19, Daniel P. Berrangé wrote:
> > This fixes some edge cases in endian handling in the VNC server. These
> > bugs are rarely going to be visible by default, since most servers will
> > negotiate encoding formats / framebuffer formats that avoid hitting
> > the problem scenarios.
> >
> > In v2:
> >
> > - Rename 'client_bo' to 'client_endian' for reviewer clarity
> > - Rename 'native' to 'native_endian' for code consistency
> >
> > Daniel P. Berrangé (3):
> > ui/vnc.c: replace big endian flag with byte order value
> > ui/vnc: take account of client byte order in pixman format
> > ui/vnc: fix tight palette pixel encoding for 8/16-bpp formats
>
> Hi!
>
> Is there anything in there which is relevant for qemu-stable?
I've not seen anyone raise these issues, since basically every serious
VNC client supports 'tight' encoding and it is very rare to run anything
other than true colour mode these days.
None the less these are clear bug fixes, so valid to pull all three
patches into stable if desired.
With regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
prev parent reply other threads:[~2025-05-30 10:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-14 11:19 [PATCH v2 0/3] ui/vnc: fix some endian problems Daniel P. Berrangé
2025-05-14 11:19 ` [PATCH v2 1/3] ui/vnc.c: replace big endian flag with byte order value Daniel P. Berrangé
2025-05-14 12:18 ` BALATON Zoltan
2025-05-14 14:32 ` Philippe Mathieu-Daudé
2025-05-14 11:19 ` [PATCH v2 2/3] ui/vnc: take account of client byte order in pixman format Daniel P. Berrangé
2025-05-14 11:19 ` [PATCH v2 3/3] ui/vnc: fix tight palette pixel encoding for 8/16-bpp formats Daniel P. Berrangé
2025-05-24 10:32 ` [PATCH v2 0/3] ui/vnc: fix some endian problems Michael Tokarev
2025-05-30 10:13 ` Daniel P. Berrangé [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=aDmExrPVuuwSfZHA@redhat.com \
--to=berrange@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=mjt@tls.msk.ru \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.