From: BALATON Zoltan <balaton@eik.bme.hu>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: qemu-trivial@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] vmware_vga: Cleanup and allow simple drivers to work without the fifo
Date: Wed, 22 Aug 2012 12:19:52 +0200 (CEST) [thread overview]
Message-ID: <Pine.GSO.4.64.1208221214550.8637@mono> (raw)
In-Reply-To: <5034926B.5020808@web.de>
On Wed, 22 Aug 2012, Jan Kiszka wrote:
> This is a rather big patch. I strongly suspect you can break it up into
> smaller pieces that address separate aspects one-by-one. Also, it is
> definitely to heavy for "qemu-trivial".
Despite its size the changes included are fairly simple but I can try to
break it up. I've sent it to qemu-trivial because it may meet the "Do not
fall under an actively maintained subsystem." category as I've found no
maintainer for this part. Should I send the revisions only to qemu-devel
then?
Thanks,
BALATON Zoltan
next prev parent reply other threads:[~2012-08-22 10:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-21 21:33 [Qemu-devel] [PATCH] vmware_vga: Cleanup and allow simple drivers to work without the fifo BALATON Zoltan
2012-08-22 8:03 ` Jan Kiszka
2012-08-22 10:19 ` BALATON Zoltan [this message]
2012-08-22 15:23 ` Jan Kiszka
2012-08-24 11:07 ` Stefan Hajnoczi
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=Pine.GSO.4.64.1208221214550.8637@mono \
--to=balaton@eik.bme.hu \
--cc=jan.kiszka@web.de \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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).