From: Gerd Hoffmann <kraxel@redhat.com>
To: Peter Lieven <pl@kamp.de>
Cc: qemu-devel@nongnu.org, anthony@codemonkey.ws, xiawenc@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [PATCH] ui/vnc: fix potential memory corruption issues
Date: Mon, 30 Jun 2014 10:35:25 +0200 [thread overview]
Message-ID: <1404117325.24066.6.camel@nilsson.home.kraxel.org> (raw)
In-Reply-To: <53B1195E.9060708@kamp.de>
On Mo, 2014-06-30 at 10:01 +0200, Peter Lieven wrote:
> On 30.06.2014 09:52, Gerd Hoffmann wrote:
> > So this basically makes vnc work correctly in case guest surface and
> > server surface have different sizes, then fixes the two bugs on top of
> > that. And it obsoletes the other corruption patch send Friday.
> > Correct?
>
> Yes and yes.
Good, so I'm reading the code correctly ;)
Can you put that information into the patch description please?
Otherwise the patch is fine.
thanks,
Gerd
prev parent reply other threads:[~2014-06-30 8:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-30 7:24 [Qemu-devel] [PATCH] ui/vnc: fix potential memory corruption issues Peter Lieven
2014-06-30 7:52 ` Gerd Hoffmann
2014-06-30 8:01 ` Peter Lieven
2014-06-30 8:35 ` Gerd Hoffmann [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=1404117325.24066.6.camel@nilsson.home.kraxel.org \
--to=kraxel@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=pl@kamp.de \
--cc=qemu-devel@nongnu.org \
--cc=xiawenc@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).