qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2] qxl-render: add more sanity checks
Date: Fri, 29 Aug 2014 12:39:32 +0200	[thread overview]
Message-ID: <1409308772.3093.4.camel@nilsson.home.kraxel.org> (raw)
In-Reply-To: <20140829094625.GE2398@work-vm>

  Hi,

> Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
> 
> Should this go for stable as well?

Yep.  Added cc qemu-stable.

> (I was worried for a sec about what happens if right=width or bottom=height;
> but looking at the code below it I think it's a dirty from left..(right-1) 
> so we're OK?)

Correct.

cheers,
  Gerd

  reply	other threads:[~2014-08-29 10:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-29  7:56 [Qemu-devel] [PATCH v2] qxl-render: add more sanity checks Gerd Hoffmann
2014-08-29  9:46 ` Dr. David Alan Gilbert
2014-08-29 10:39   ` Gerd Hoffmann [this message]
2014-08-29 12:09 ` Eric Blake
2014-08-29 12:51   ` Gerd Hoffmann

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=1409308772.3093.4.camel@nilsson.home.kraxel.org \
    --to=kraxel@redhat.com \
    --cc=dgilbert@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).