From: Heiko Carstens <heiko.carstens@de.ibm.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: linux-kernel@vger.kernel.org,
Christian Borntraeger <borntraeger@de.ibm.com>,
linux-s390@vger.kernel.org, Thomas Huth <thuth@redhat.com>,
Cornelia Huck <cohuck@redhat.com>,
Halil Pasic <pasic@linux.vnet.ibm.com>,
Martin Schwidefsky <schwidefsky@de.ibm.com>
Subject: Re: [PATCH v2 2/2] s390/virtio: add BSD license to virtio-ccw
Date: Fri, 24 Nov 2017 18:18:35 +0100 [thread overview]
Message-ID: <20171124171834.GA2857@osiris> (raw)
In-Reply-To: <20171124190132-mutt-send-email-mst@kernel.org>
On Fri, Nov 24, 2017 at 07:02:41PM +0200, Michael S. Tsirkin wrote:
> On Fri, Nov 24, 2017 at 05:53:01PM +0100, Heiko Carstens wrote:
> > > > Is there any reason to add the whole BSD 3 clause license text? I'd prefer
> > > > if it would be just the simple new SPDX-License-Identifier above.
>
> I added it for consistency with other virtio headers.
Well, one of the points of the SPDX tags is to avoid the countless
duplication of license texts. Adding a license text is easy, removing it
again later is not as easy. Therefore I would prefer to avoid the
duplication here again.
Cornelia, Christian, any opinion here?
Thanks.
next prev parent reply other threads:[~2017-11-24 17:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-24 5:21 [PATCH v2 1/2] s390/virtio: remove the old KVM virtio headers Michael S. Tsirkin
2017-11-24 5:21 ` [PATCH v2 2/2] s390/virtio: add BSD license to virtio-ccw Michael S. Tsirkin
2017-11-24 9:09 ` Cornelia Huck
2017-11-24 16:24 ` Michael S. Tsirkin
2017-11-24 14:09 ` Heiko Carstens
2017-11-24 16:21 ` Michael S. Tsirkin
2017-11-24 16:53 ` Heiko Carstens
2017-11-24 17:02 ` Michael S. Tsirkin
2017-11-24 17:18 ` Heiko Carstens [this message]
2017-11-27 8:15 ` Christian Borntraeger
2017-11-27 9:16 ` Cornelia Huck
2017-11-24 5:29 ` [PATCH v2 1/2] s390/virtio: remove the old KVM virtio headers Thomas Huth
2017-11-26 13:54 ` kbuild test robot
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=20171124171834.GA2857@osiris \
--to=heiko.carstens@de.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=mst@redhat.com \
--cc=pasic@linux.vnet.ibm.com \
--cc=schwidefsky@de.ibm.com \
--cc=thuth@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.