qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Marcel Apfelbaum <marcel.apfelbaum@gmail.com>
To: qemu-devel@nongnu.org, kraxel@redhat.com
Cc: alex.williamson@redhat.com, hqm03ster@gmail.com
Subject: Re: [Qemu-devel] [PATCH V3 0/3] ramfb improvements
Date: Thu, 23 May 2019 17:46:13 +0300	[thread overview]
Message-ID: <49137f7b-16a7-7b3f-7407-7748ed2614ad@gmail.com> (raw)
In-Reply-To: <20190513115731.17588-1-marcel.apfelbaum@gmail.com>



On 5/13/19 2:57 PM, Marcel Apfelbaum wrote:
> Please see the description in each patch.
>
> Qiming, thanks for taking the time to upstream your patches!
> Marcel

Hi Gerd,

Are the patches ready or do you have some comments?

Thanks,
Marcel

> V2 - V3:
>   - rebase to latest master
>   - send as new series
>   - use QEMU coding conventions
>   - fixed malformed patches (maybe I didn't import them right)
>
> Hou Qiming (3):
>    hw/display/ramfb: fix guest memory un-mapping
>    hw/display/ramfb: lock guest resolution after it's set
>    hw/display/ramfb: initialize fw-config space with xres/ yres
>
>   hw/display/ramfb-standalone.c | 12 ++++-
>   hw/display/ramfb.c            | 89 ++++++++++++++++++++++++++++-------
>   hw/vfio/display.c             |  4 +-
>   include/hw/display/ramfb.h    |  2 +-
>   stubs/ramfb.c                 |  2 +-
>   5 files changed, 88 insertions(+), 21 deletions(-)
>



      parent reply	other threads:[~2019-05-23 14:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-13 11:57 [Qemu-devel] [PATCH V3 0/3] ramfb improvements Marcel Apfelbaum
2019-05-13 11:57 ` [Qemu-devel] [PATCH V3 1/3] hw/display/ramfb: fix guest memory un-mapping Marcel Apfelbaum
2019-05-13 11:57 ` [Qemu-devel] [PATCH V3 2/3] hw/display/ramfb: lock guest resolution after it's set Marcel Apfelbaum
2019-05-13 11:57 ` [Qemu-devel] [PATCH V3 3/3] hw/display/ramfb: initialize fw-config space with xres/ yres Marcel Apfelbaum
2019-05-23 14:46 ` Marcel Apfelbaum [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=49137f7b-16a7-7b3f-7407-7748ed2614ad@gmail.com \
    --to=marcel.apfelbaum@gmail.com \
    --cc=alex.williamson@redhat.com \
    --cc=hqm03ster@gmail.com \
    --cc=kraxel@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).