From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eric Blake Subject: Re: [PATCH 4/4] kvm: i386: Add classic PCI device assignment Date: Wed, 05 Sep 2012 13:24:16 -0600 Message-ID: <5047A6E0.90902@redhat.com> References: <825e653c9cfe9d8e26185917cbe1f1dd7ae299e2.1346048917.git.jan.kiszka@web.de> <503B62F4.9070500@suse.de> <87k3wjyy0e.fsf@codemonkey.ws> <503E227B.40904@suse.de> <874nndmrjs.fsf@codemonkey.ws> <50476F3E.7000100@redhat.com> <87wr081nq4.fsf@codemonkey.ws> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="------------enig5A196A4C50593B62DBB8AB5A" Cc: kvm@vger.kernel.org, "Michael S. Tsirkin" , Alexey Kardashevskiy , Marcelo Tosatti , qemu-devel@nongnu.org, Alex Williamson , Jan Kiszka , Avi Kivity , Anthony Liguori , qemu-ppc , =?UTF-8?B?QW5kcmVhcyBGw6RyYmVy?= To: Blue Swirl Return-path: In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org Sender: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org List-Id: kvm.vger.kernel.org This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig5A196A4C50593B62DBB8AB5A Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 09/05/2012 01:04 PM, Blue Swirl wrote: >> I don't mind GPLv2+, if people want to share code from QEMU in GPLv3 >> projects, GPLv2+ enables that. >=20 > The advantage of 100% GPLv2+ (or other GPLv3 compatible) would be that > QEMU could share code from GPLv3 projects, specifically latest > binutils. Reinventing a disassembler for ever growing x86 assembly is > no fun. Not quite right. If qemu is 100% GPLv2+ and binutils is GPLv3+, then binutils can borrow code from qemu and the result is that binutils is still GPLv3+; but in the converse direction, if qemu borrows code from binutils then qemu is no longer 100% GPLv2+ but becomes GPLv3+ by tainting. That is, requesting GPLv2+ allows qemu code to be reused elsewhere, but does not help qemu import external code that is not already GPLv2+. >=20 >> >> But if new code is coming in and happens to be under GPLv2, that just >> means that the contribution cannot be used outside of QEMU in a GPLv3 >> project. That's fine and that's a decision for the submitter to make.= >=20 > This policy means that we are locked in with GPLv2. I'm afraid we're already locked at GPLv2 (and not GPLv2+), for good or for bad. --=20 Eric Blake eblake@redhat.com +1-919-301-3266 Libvirt virtualization library http://libvirt.org --------------enig5A196A4C50593B62DBB8AB5A Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Public key at http://people.redhat.com/eblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iQEcBAEBCAAGBQJQR6bhAAoJEKeha0olJ0Nqox4H/1bC2GMqqd+F/WgnE1w0i2qN sVI2YhaIQ4gWTsycXhqvjUlaDtRfVBeLpE/8WbOukNIQAzMtZyTzefeuINKfnXxq /1d+KNKZDMZnIEiiHx5XN+dE3viYxlzBwhq3YC3JRxoh2prmskXYye/J3n7t9dKv lKw2f96x+sQv2NeBIw24N89pDIS9YwGI8Ifj/eDs0WuD7w+rNR+aJp6FghRh6m0Z 9V31+WvdZ2BqfS+nhbG9ys+ZLNypTX1uHbY2/A4KL2Gc2U//YmQdcJUL1suyS+hT CfoThEbPqm+ttc1fZqZ3OY66KpXVMVAgQkfuLF6fMSibjodo313V6i+R/xCPzDk= =MuzH -----END PGP SIGNATURE----- --------------enig5A196A4C50593B62DBB8AB5A--