From: "Andreas Färber" <afaerber@suse.de>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: aliguori@us.ibm.com, qemu-devel@nongnu.org, mst@redhat.com
Subject: Re: [Qemu-devel] [PATCH] Better support for dma_addr_t variables
Date: Tue, 03 Apr 2012 10:53:10 +0200 [thread overview]
Message-ID: <4F7ABA76.8030107@suse.de> (raw)
In-Reply-To: <20120403005143.GC7481@truffala.fritz.box>
Am 03.04.2012 02:51, schrieb David Gibson:
> On Mon, Apr 02, 2012 at 09:49:12AM +0200, Andreas Färber wrote:
>> Am 31.03.2012 10:50, schrieb David Gibson:
>>> On Fri, Mar 30, 2012 at 11:34:25AM +0200, Andreas Färber wrote:
>>>> Am 30.03.2012 11:32, schrieb Andreas Färber:
>>>>> Am 27.03.2012 04:43, schrieb David Gibson:
>>>>>> diff --git a/hw/qdev-dma.h b/hw/qdev-dma.h
>>>>>> new file mode 100644
>>>>>> index 0000000..e407771
>>>>>> --- /dev/null
>>>>>> +++ b/hw/qdev-dma.h
>>>>>> @@ -0,0 +1,4 @@
>>>>>> +#include "qdev-addr.h"
>>>>>> +
>>>>>> +#define DEFINE_PROP_DMAADDR(_n, _s, _f, _d) \
>>>>>> + DEFINE_PROP_TADDR(_n, _s, _f, _d)
>>>>>
>>>>> Is a new header just for this really needed? It's not being used in this
>>>>> patch, so its necessity is hard to judge. ;)
>>>>
>>>> Additionally it's missing a license notice.
>>>
>>> Just like qdev-addr.h. And qdev.h for that matter.
>>>
>>> You seriously want a license notice for two lines of trivial macro?
>>
>> Yes, the issue here is under what license the file is. It's a new file,
>> so in lack of a license statement is it under GPLv2 because QEMU as a
>> whole currently is? Thus a header explicitly saying that it's under
>> GPLv2+ (or BSD or MIT/X11 or ...) would be appreciated to avoid further
>> complications. Compare our GPLv2+ relicensing page:
>>
>> http://wiki.qemu.org/Relicensing
>
> It's 4 trivial lines. Well under the copyrightability threshold even
> by the paranoid estimates of IBM Legal.
Tell that to your IBM colleague. We had an argument about 1 line of
trivial code replacement (not even new code) that kept us from
relicensing target-unicore32/helper.c just recently.
This is not me who's being paranoid about lines of code, really. I've
even heard that header files may not even be the subject of licenses at
all in some legislations. I'm just picky and sometimes spot the odd sock
from afar. ;)
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2012-04-03 8:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-27 2:43 [Qemu-devel] [PATCH] Better support for dma_addr_t variables David Gibson
2012-03-30 2:46 ` David Gibson
2012-03-30 9:32 ` Andreas Färber
2012-03-30 9:34 ` Andreas Färber
2012-03-31 8:50 ` David Gibson
2012-04-02 7:49 ` Andreas Färber
2012-04-03 0:51 ` David Gibson
2012-04-03 7:12 ` Peter Maydell
2012-04-03 8:53 ` Andreas Färber [this message]
2012-04-04 0:12 ` David Gibson
2012-03-31 8:49 ` David Gibson
2012-04-01 9:17 ` Michael S. Tsirkin
2012-04-01 9:21 ` David Gibson
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=4F7ABA76.8030107@suse.de \
--to=afaerber@suse.de \
--cc=aliguori@us.ibm.com \
--cc=david@gibson.dropbear.id.au \
--cc=mst@redhat.com \
--cc=qemu-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).