qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: Alon Levy <alevy@redhat.com>,
	qemu-devel@nongnu.org, Dunrong Huang <riegamaths@gmail.com>
Subject: Re: [Qemu-devel] [PATCH] qxl/update_area_io: cleanup invalid parameters handling
Date: Thu, 20 Sep 2012 08:50:09 +0200	[thread overview]
Message-ID: <505ABCA1.2020104@redhat.com> (raw)
In-Reply-To: <505ABB0E.9030305@msgid.tls.msk.ru>

On 09/20/12 08:43, Michael Tokarev wrote:
> For now it is irrelevant actually, since right after the
> switch we already have "return", so "break" is now the
> same as "return".  For future it might not be the case.

Oh, right.  Patch added to spice patch queue.

thanks,
  Gerd

      reply	other threads:[~2012-09-20  6:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-19 13:41 [Qemu-devel] [PATCH] qxl/update_area_io: cleanup invalid parameters handling Michael Tokarev
2012-09-20  6:41 ` Gerd Hoffmann
2012-09-20  6:43   ` Michael Tokarev
2012-09-20  6:50     ` 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=505ABCA1.2020104@redhat.com \
    --to=kraxel@redhat.com \
    --cc=alevy@redhat.com \
    --cc=mjt@tls.msk.ru \
    --cc=qemu-devel@nongnu.org \
    --cc=riegamaths@gmail.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).