From: Gerd Hoffmann <kraxel@redhat.com>
To: qemu-devel@nongnu.org
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Alex Williamson <alex.williamson@redhat.com>,
lersek@redhat.com, Gerd Hoffmann <kraxel@redhat.com>,
hqm03ster@gmail.com
Subject: [PATCH v2 0/6] ramfb: a bunch of reverts and fixes
Date: Wed, 29 Apr 2020 13:52:30 +0200 [thread overview]
Message-ID: <20200429115236.28709-1-kraxel@redhat.com> (raw)
Even though these are bugfixes this is probably 5.1 material
at this point ...
v2: reorder patches, add patch #6, pick up acks & reviews.
Gerd Hoffmann (6):
Revert "hw/display/ramfb: initialize fw-config space with xres/ yres"
Revert "hw/display/ramfb: lock guest resolution after it's set"
ramfb: drop leftover debug message
ramfb: don't update RAMFBState on errors
ramfb: add sanity checks to ramfb_create_display_surface
ramfb: fix size calculation
include/hw/display/ramfb.h | 2 +-
hw/display/ramfb-standalone.c | 12 +-----
hw/display/ramfb.c | 78 +++++++++++++----------------------
hw/vfio/display.c | 4 +-
stubs/ramfb.c | 2 +-
5 files changed, 34 insertions(+), 64 deletions(-)
--
2.18.2
next reply other threads:[~2020-04-29 11:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-29 11:52 Gerd Hoffmann [this message]
2020-04-29 11:52 ` [PATCH v2 1/6] Revert "hw/display/ramfb: initialize fw-config space with xres/ yres" Gerd Hoffmann
2020-04-29 11:52 ` [PATCH v2 2/6] Revert "hw/display/ramfb: lock guest resolution after it's set" Gerd Hoffmann
2020-04-29 11:52 ` [PATCH v2 3/6] ramfb: drop leftover debug message Gerd Hoffmann
2020-04-29 11:52 ` [PATCH v2 4/6] ramfb: don't update RAMFBState on errors Gerd Hoffmann
2020-04-29 11:52 ` [PATCH v2 5/6] ramfb: add sanity checks to ramfb_create_display_surface Gerd Hoffmann
2020-04-29 19:37 ` Laszlo Ersek
2020-04-29 11:52 ` [PATCH v2 6/6] ramfb: fix size calculation Gerd Hoffmann
2020-04-29 16:37 ` [PATCH v2 0/6] ramfb: a bunch of reverts and fixes no-reply
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=20200429115236.28709-1-kraxel@redhat.com \
--to=kraxel@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=hqm03ster@gmail.com \
--cc=lersek@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@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 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).