From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:50498) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Uhg4O-0004RH-Gz for qemu-devel@nongnu.org; Wed, 29 May 2013 09:05:41 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Uhg4J-0007Js-Se for qemu-devel@nongnu.org; Wed, 29 May 2013 09:05:36 -0400 Received: from mail-oa0-f42.google.com ([209.85.219.42]:64409) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Uhg4J-0007J5-Nc for qemu-devel@nongnu.org; Wed, 29 May 2013 09:05:31 -0400 Received: by mail-oa0-f42.google.com with SMTP id i10so11587558oag.1 for ; Wed, 29 May 2013 06:05:31 -0700 (PDT) From: Anthony Liguori In-Reply-To: <87ip22od5f.fsf@rustcorp.com.au> References: <20130526181017.GB3115@redhat.com> <51A253C6.7060303@redhat.com> <20130526183747.GB3427@redhat.com> <51A25A2D.8030700@redhat.com> <20130526200251.GA4305@redhat.com> <51A26E95.5000207@redhat.com> <878v314gb2.fsf@codemonkey.ws> <20130526214213.GB4828@redhat.com> <87txlp1bsy.fsf@codemonkey.ws> <20130527150217.GA16852@redhat.com> <87bo7wflhk.fsf@codemonkey.ws> <87ip22od5f.fsf@rustcorp.com.au> Date: Wed, 29 May 2013 08:05:29 -0500 Message-ID: <87hahmq6li.fsf@codemonkey.ws> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: [Qemu-devel] [PATCH v2 00/11] qemu: use virtio linux headers in portable code List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Rusty Russell , "Michael S. Tsirkin" Cc: Paolo Bonzini , virtualization , qemu-devel@nongnu.org, Peter Maydell Rusty Russell writes: > Anthony Liguori writes: >> The headers say they are BSD licensed... but they include a GPLv2+ >> header. Doesn't make a lot of sense, does it? > > It makes perfect sense: you're overthinking it. It just means that > copying the BSD headers outside Linux is encouraged. Copying by hand and modifying. This patch series attempts to do it automatically within QEMU. > And it's clearly nonsensical to claim the GPL on kernel headers means > that userspace needs to be GPL. So please ignore this licensing > red-herring. You're missing context, I suspect. This series is trying to automatically copy the headers from Linux. We currently have a manually copied version. The headers are not currently well suited for automatic copying because (1) they use kernel types (2) they pull in dependencies from throughout the kernel. This discussion comes down to whether we want to make it easier to automatically copy the headers or do we maintain the status quo and require manual munging to pull in the headers. Regards, Anthony Liguori > > And we'll bikeshed the headers in the standard when we have to :) They > certainly don't need to be cut&paste into the kernel sources. > > Cheers, > Rusty.