From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:46477) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YnRCf-0005A7-Or for qemu-devel@nongnu.org; Wed, 29 Apr 2015 08:35:02 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YnRCc-0005NR-DB for qemu-devel@nongnu.org; Wed, 29 Apr 2015 08:35:01 -0400 Received: from mx1.redhat.com ([209.132.183.28]:51150) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YnRCc-0005NG-4o for qemu-devel@nongnu.org; Wed, 29 Apr 2015 08:34:58 -0400 Message-ID: <5540CFC4.2070903@redhat.com> Date: Wed, 29 Apr 2015 06:34:12 -0600 From: Eric Blake MIME-Version: 1.0 References: <1428206887-7921-1-git-send-email-eblake@redhat.com> <87618gnyex.fsf@blackfin.pond.sub.org> <553FC888.6090305@redhat.com> <87fv7jfn0f.fsf@blackfin.pond.sub.org> In-Reply-To: <87fv7jfn0f.fsf@blackfin.pond.sub.org> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="sxNFW1BlmdINFM3MoE15LjGKurchRcId0" Subject: Re: [Qemu-devel] [PATCH v6 00/36] drop qapi nested structs List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Markus Armbruster Cc: kwolf@redhat.com, berto@igalia.com, "Michael S. Tsirkin" , Michael Roth , qemu-devel@nongnu.org, Luiz Capitulino This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --sxNFW1BlmdINFM3MoE15LjGKurchRcId0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 04/29/2015 12:48 AM, Markus Armbruster wrote: > General question first: through which tree should this go? >=20 > MAINTAINERS doesn't cover the QAPI generators. Closest related stanza > is QAPI (Luiz, Michael R.). Should it cover the generators? Next > closest is QAPI Schema (Luiz, you, myself). >=20 > For completeness: because we touch qmp_query_pci_bridge() and > qmp_query_pci_devices(), get_maintainers.pl also fingers the PCI tree. >=20 > If nobody objects, I can take it through my tree. Cc'ing the > maintainers just mentioned to give them a chance to chime in. Works for me, but that means we may want to also add the qapi generators into MAINTAINERS along-side QAPI Schema for future changes. Of course, as a separate patch. >> Easier as a followup? Respin just the one patch? Or bite the bullet an= d >> rebase the entire series (fixing the other trivial items and adding R-= b >> along the way)? >=20 > I think we can either >=20 > * Respin, but keep the changes really simple. Feel free to leave some > issues to followup patches. Changes in the qapi schema (new structs) require a rebase, so respin on its way. --=20 Eric Blake eblake redhat com +1-919-301-3266 Libvirt virtualization library http://libvirt.org --sxNFW1BlmdINFM3MoE15LjGKurchRcId0 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 Comment: Public key at http://people.redhat.com/eblake/eblake.gpg Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBCAAGBQJVQM/EAAoJEKeha0olJ0NqJWQH/2cAEvHoZcOWHxkCiPRWa7Aq moU/S7QT5mAewoYZCYstEax1cAX8GT/2MBY69B8jBudgIwPdlSZtWhhTDLsHa/uO O5cqOpvk4DIeIKHFc7Ldwz86OA4HrqF6mojcoNn4NUCZrk8hlge3wFzQjh2zUsfr 7xHy1xJ0riPZM5/ZKVZgOZcJRAn4+gUaO6FRqFJg6caGk9FsRWsMMeeJItZHmP79 BX1H4iyEqPQbJfGaQrTmsQ5E5E+KcWH5z00iIVQUdNdx/oHBIk91XQw511mHhCcX 0DGAUhsYutrn+3+Y/dBRkaADEAyYR8DmnVTzmyXSLbhG7CIKdjnf/JW5CnyMsIM= =QO6U -----END PGP SIGNATURE----- --sxNFW1BlmdINFM3MoE15LjGKurchRcId0--