From: "Daniel P. Berrange" <berrange@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: Olivier Matz <olivier.matz@6wind.com>,
kvm@vger.kernel.org, claudio.fontana@huawei.com,
David Marchand <david.marchand@6wind.com>,
qemu-devel@nongnu.org, pbonzini@redhat.com,
jani.kokkonen@huawei.com, cam@cs.ualberta.ca
Subject: Re: [Qemu-devel] [PATCH v2 1/2] contrib: add ivshmem client and server
Date: Mon, 21 Jul 2014 15:30:01 +0100 [thread overview]
Message-ID: <20140721143001.GF3829@redhat.com> (raw)
In-Reply-To: <53CD21E1.1010908@redhat.com>
On Mon, Jul 21, 2014 at 08:21:21AM -0600, Eric Blake wrote:
> On 07/20/2014 03:38 AM, David Marchand wrote:
> > When using ivshmem devices, notifications between guests can be sent as
> > interrupts using a ivshmem-server (typical use described in documentation).
> > The client is provided as a debug tool.
> >
> > Signed-off-by: Olivier Matz <olivier.matz@6wind.com>
> > Signed-off-by: David Marchand <david.marchand@6wind.com>
> > ---
> > contrib/ivshmem-client/Makefile | 26 ++
>
> > +++ b/contrib/ivshmem-client/Makefile
> > @@ -0,0 +1,26 @@
> > +# Copyright 2014 6WIND S.A.
> > +# All rights reserved
>
> This file has no other license, and is therefore incompatible with
> GPLv2. You'll need to resubmit under an appropriately open license.
>
> > +++ b/contrib/ivshmem-client/ivshmem-client.h
> > @@ -0,0 +1,238 @@
> > +/*
> > + * Copyright(c) 2014 6WIND S.A.
> > + * All rights reserved.
> > + *
> > + * This work is licensed under the terms of the GNU GPL, version 2. See
> > + * the COPYING file in the top-level directory.
>
> I'm not a lawyer, but to me, this license is self-contradictory. You
> can't have "All rights reserved" and still be GPL, because the point of
> the GPL is that you are NOT reserving all rights, but explicitly
> granting your user various rights (on condition that they likewise grant
> those rights to others). But you're not the only file in the qemu code
> base with this questionable mix.
In any case adding the term 'All rights reserved' is said to be redundant
obsolete these days
https://en.wikipedia.org/wiki/All_rights_reserved#Obsolescence
Regards,
Daniel
--
|: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org -o- http://virt-manager.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|
next prev parent reply other threads:[~2014-07-21 14:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-20 9:38 [Qemu-devel] [PATCH v2 0/2] ivshmem: update documentation, add client/server tools David Marchand
2014-07-20 9:38 ` [Qemu-devel] [PATCH v2 1/2] contrib: add ivshmem client and server David Marchand
2014-07-21 14:21 ` Eric Blake
2014-07-21 14:30 ` Daniel P. Berrange [this message]
2014-07-21 15:26 ` David Marchand
2014-07-21 17:35 ` Markus Armbruster
2014-08-08 8:49 ` David Marchand
2014-07-20 9:38 ` [Qemu-devel] [PATCH v2 2/2] docs: update ivshmem device spec David Marchand
2014-07-21 8:19 ` Claudio Fontana
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=20140721143001.GF3829@redhat.com \
--to=berrange@redhat.com \
--cc=cam@cs.ualberta.ca \
--cc=claudio.fontana@huawei.com \
--cc=david.marchand@6wind.com \
--cc=eblake@redhat.com \
--cc=jani.kokkonen@huawei.com \
--cc=kvm@vger.kernel.org \
--cc=olivier.matz@6wind.com \
--cc=pbonzini@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).