From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:35454) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YZ1AK-0006M4-Pr for qemu-devel@nongnu.org; Fri, 20 Mar 2015 13:57:02 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YZ1AH-0000OW-Jv for qemu-devel@nongnu.org; Fri, 20 Mar 2015 13:57:00 -0400 Received: from mx1.redhat.com ([209.132.183.28]:55441) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YZ1AH-0000OM-CF for qemu-devel@nongnu.org; Fri, 20 Mar 2015 13:56:57 -0400 Message-ID: <550C5F4A.2080001@redhat.com> Date: Fri, 20 Mar 2015 18:56:26 +0100 From: Paolo Bonzini MIME-Version: 1.0 References: <1426791181-23831-1-git-send-email-marcel@redhat.com> <550B4387.1030308@redhat.com> <550BDC55.7080505@redhat.com> In-Reply-To: <550BDC55.7080505@redhat.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH V6 for-2.3 00/26] hw/pc: implement multiple primary busses for pc machines List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Marcel Apfelbaum , qemu-devel@nongnu.org Cc: quintela@redhat.com, mst@redhat.com, agraf@suse.de, alex.williamson@redhat.com, kevin@koconnor.net, kraxel@redhat.com, amit.shah@redhat.com, imammedo@redhat.com, rth@twiddle.net, leon.alrae@imgtec.com, aurelien@aurel32.net, hare@suse.de On 20/03/2015 09:37, Marcel Apfelbaum wrote: >> I think this should not be committed to 2.3 after -rc0. > While I agree that looking at the above the series do not > fit for 2.3, I still think the risk is not big because: > - The biggest amount of modifications are in pci_bus/pci_host > and *is only* a movement of code into a new file, > no changes at all (This cover almost half of the series changes) > - The series does not intervene with usual process, meaning if > pxb is not used, it will work exactly like before > - The bios already supports pxb for this release, is a pity to wait > for another QEMU version. > - The series were in mailing list for more than a month before rc, > but the real review process started at rc time. > (begging the question what a non-maintainer must do to get its code in > time) > - The series is mature, rebased on the latest QEMU > and was reviewed in depth and tested by the community. I understand, but you have to draw a line somewhere. The easiest place to draw the line is 2.3.0-rc0. Maintainers can already prepare branches with patches destined to 2.4, and these 26 can be included there. As far as you are concerned, if the code is ready you can stop worrying about it. The problem isn't non-maintainer vs. maintainer. There was a dependency on Igor's series, which took some time to get in---partly because it was included in a 100-patch pull request, which isn't exactly the preferred way to send pull request in absence of a serious effort on continuous integration of maintainer branches. Paolo