From: Jan Kiszka <jan.kiszka@web.de>
To: BALATON Zoltan <balaton@eik.bme.hu>
Cc: qemu-trivial@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-trivial] [PATCH] vmware_vga: Cleanup and allow simple drivers to work without the fifo
Date: Wed, 22 Aug 2012 17:23:49 +0200 [thread overview]
Message-ID: <5034F985.7020202@web.de> (raw)
In-Reply-To: <Pine.GSO.4.64.1208221214550.8637@mono>
[-- Attachment #1: Type: text/plain, Size: 726 bytes --]
On 2012-08-22 12:19, BALATON Zoltan wrote:
> 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."
But that doesn't make it trivial, rather harder (if no one reviewed it).
> category as I've found
> no maintainer for this part. Should I send the revisions only to
> qemu-devel then?
Yes, that's more appropriate IMHO.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Jan Kiszka <jan.kiszka@web.de>
To: BALATON Zoltan <balaton@eik.bme.hu>
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 17:23:49 +0200 [thread overview]
Message-ID: <5034F985.7020202@web.de> (raw)
In-Reply-To: <Pine.GSO.4.64.1208221214550.8637@mono>
[-- Attachment #1: Type: text/plain, Size: 726 bytes --]
On 2012-08-22 12:19, BALATON Zoltan wrote:
> 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."
But that doesn't make it trivial, rather harder (if no one reviewed it).
> category as I've found
> no maintainer for this part. Should I send the revisions only to
> qemu-devel then?
Yes, that's more appropriate IMHO.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
next prev parent reply other threads:[~2012-08-22 15:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-21 21:33 [Qemu-trivial] [PATCH] vmware_vga: Cleanup and allow simple drivers to work without the fifo BALATON Zoltan
2012-08-21 21:33 ` [Qemu-devel] " BALATON Zoltan
2012-08-22 8:03 ` [Qemu-trivial] " Jan Kiszka
2012-08-22 8:03 ` [Qemu-devel] " Jan Kiszka
2012-08-22 10:19 ` [Qemu-trivial] " BALATON Zoltan
2012-08-22 10:19 ` [Qemu-devel] " BALATON Zoltan
2012-08-22 15:23 ` Jan Kiszka [this message]
2012-08-22 15:23 ` Jan Kiszka
2012-08-24 11:07 ` [Qemu-trivial] " Stefan Hajnoczi
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=5034F985.7020202@web.de \
--to=jan.kiszka@web.de \
--cc=balaton@eik.bme.hu \
--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 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.