From: "Andreas Färber" <afaerber@suse.de>
To: Stephan Kulow <coolo@suse.de>, qemu-devel@nongnu.org
Cc: Gerd Hoffmann <kraxel@redhat.com>, Anthony Liguori <aliguori@amazon.com>
Subject: Re: [Qemu-devel] [PULL for-2.1 1/2] fix full frame updates for VNC clients
Date: Thu, 24 Jul 2014 15:57:18 +0200 [thread overview]
Message-ID: <53D110BE.7050104@suse.de> (raw)
In-Reply-To: <53D10E16.7060105@suse.de>
Am 24.07.2014 15:45, schrieb Stephan Kulow:
> On 24.07.2014 14:30, Andreas Färber wrote:
>> Am 24.07.2014 10:28, schrieb Gerd Hoffmann:
>>> From: Stephan Kulow <coolo@suse.de>
>>>
>>> If the client asks for !incremental frame updates, it has lost its content
>>> so dirty doesn't matter - it has to see the full frame, so setting force_update
>>>
>>
>> Can you please sign off your (trivial) patch via reply?
>
> You mean confirming it was my patch? Yes, it was.
Yes, in the sense of written-by-you - that's expected to be indicated
the kernel way through a "Signed-off-by: Your name <your@email>" line,
usually automated via git commit -s.
Cheers,
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2014-07-24 13:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-24 8:28 [Qemu-devel] [PULL for-2.1 0/2] vnc: fix two vnc update issues Gerd Hoffmann
2014-07-24 8:28 ` [Qemu-devel] [PULL for-2.1 1/2] fix full frame updates for VNC clients Gerd Hoffmann
2014-07-24 12:30 ` Andreas Färber
2014-07-24 13:45 ` Stephan Kulow
2014-07-24 13:57 ` Andreas Färber [this message]
2014-07-24 8:28 ` [Qemu-devel] [PULL for-2.1 2/2] vnc update fix Gerd Hoffmann
2014-07-24 11:48 ` [Qemu-devel] [PULL for-2.1 0/2] vnc: fix two vnc update issues Peter Maydell
2014-07-24 12:20 ` Andreas Färber
2014-07-24 14:10 ` Gerd Hoffmann
2014-07-24 14:22 ` Peter Maydell
2014-07-25 7:45 ` Gerd Hoffmann
2014-07-25 11:52 ` Peter Maydell
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=53D110BE.7050104@suse.de \
--to=afaerber@suse.de \
--cc=aliguori@amazon.com \
--cc=coolo@suse.de \
--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 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.