From: Felipe Balbi <balbi@ti.com>
To: Pavel Machek <pavel@denx.de>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Stefan Roese <sr@denx.de>, <monstr@monstr.eu>, <balbi@ti.com>,
<linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>,
Wolfgang Denk <wd@denx.de>
Subject: Re: SPDX-License-Identifier
Date: Wed, 25 Feb 2015 16:00:47 -0600 [thread overview]
Message-ID: <20150225220047.GS11136@saruman.tx.rr.com> (raw)
In-Reply-To: <20150225214950.GB29527@amd>
[-- Attachment #1: Type: text/plain, Size: 1949 bytes --]
On Wed, Feb 25, 2015 at 10:49:51PM +0100, Pavel Machek wrote:
> Hi!
>
> > > >Is one tag per directory sufficient? Is one tag per file sufficient?
> > > >How about one tag per package? If package, then isn't a single tag for
> > > >the whole kernel source tree sufficient, as we all know the overall
> > > >license for the kernel source tree.
> > >
> > > We really need one tag per file.
> >
> > I fail to see the justification for this, why? Why not per directory?
> > Why not per function? Why not per driver? Why not per line? Why not
> > per project? Who has dictated this seemingly arbitrary rule?
>
> That's how licenses are done today.
>
> Why would I like to see SPDX?
>
> So that GPL header at begining of each file becomes one line... and so
> that if it is BSD/GPL dual licensed is plain to see, and I don't have
> to read the notices saying "oh this is gpl.. but if you want to,
> delete gpl above and use license below".
why isn't git grep -e 'MODULE_LICENSE' enough ? It's also a single line
and gives you the license for that driver.
> > Our DCO process ensures that.
> >
> > > - Some parts of the Linux source code are also used by other projects.
> > > Or are derived from other projects. Because of this they are
> > > explicitly licensed under different licenses than the GPLv2
> > > (compatible to it though of course). Or are dual-licensed. So that
> > > they can be used by these other projects.
> >
> > That's fine, we encourage that and want to see that happen. How will
> > SPDX change that at all? It's obvious as to the license of the files
> > that this happens with, why do anything extra?
>
> Well, sometimes parsing license agreements at the top of file is
> interesting, that's where SPDX would help, and that's why having
> single SPDX per linux kernel would not work.
if you can parse SPDX, why can't you parse MODULE_LICENSE() ?
--
balbi
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-02-25 22:01 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-19 9:40 [PATCH RFC] usb: gadget: Add xilinx axi usb2 device support Subbaraya Sundeep Bhatta
2014-02-20 18:23 ` Felipe Balbi
2014-02-21 6:38 ` Michal Simek
2014-02-21 16:04 ` Greg Kroah-Hartman
2014-02-21 16:04 ` Michal Simek
2014-02-21 16:12 ` SPDX-License-Identifier (was: Re: [PATCH RFC] usb: gadget: Add xilinx axi usb2 device support) Felipe Balbi
2014-02-21 16:18 ` SPDX-License-Identifier Michal Simek
2014-02-21 16:20 ` SPDX-License-Identifier Felipe Balbi
2014-02-21 16:56 ` SPDX-License-Identifier Greg Kroah-Hartman
2014-02-21 17:26 ` SPDX-License-Identifier Michal Simek
2014-02-21 17:57 ` SPDX-License-Identifier Greg Kroah-Hartman
2014-02-21 19:01 ` SPDX-License-Identifier Theodore Ts'o
2014-02-24 10:12 ` SPDX-License-Identifier Michal Simek
2014-02-24 13:41 ` SPDX-License-Identifier Theodore Ts'o
2014-02-24 14:03 ` SPDX-License-Identifier Michal Simek
2014-02-24 14:26 ` SPDX-License-Identifier Greg Kroah-Hartman
2014-02-25 12:10 ` SPDX-License-Identifier One Thousand Gnomes
2014-02-25 12:25 ` SPDX-License-Identifier Geert Uytterhoeven
2015-02-02 15:43 ` SPDX-License-Identifier Stefan Roese
2015-02-02 16:06 ` SPDX-License-Identifier Greg Kroah-Hartman
2015-02-04 16:41 ` SPDX-License-Identifier Stefan Roese
2015-02-05 4:21 ` SPDX-License-Identifier Theodore Ts'o
2015-02-05 6:41 ` SPDX-License-Identifier Greg Kroah-Hartman
2015-02-25 21:49 ` SPDX-License-Identifier Pavel Machek
2015-02-25 22:00 ` Felipe Balbi [this message]
2015-02-26 21:49 ` SPDX-License-Identifier Pavel Machek
2015-02-26 10:26 ` SPDX-License-Identifier One Thousand Gnomes
2015-02-26 13:39 ` SPDX-License-Identifier Theodore Ts'o
2015-02-26 21:53 ` SPDX-License-Identifier Pavel Machek
2015-02-05 11:49 ` SPDX-License-Identifier One Thousand Gnomes
2014-02-21 16:23 ` [PATCH RFC] usb: gadget: Add xilinx axi usb2 device support Greg Kroah-Hartman
2014-02-21 11:27 ` Subbaraya Sundeep Bhatta
2014-02-21 15:39 ` Felipe Balbi
2014-03-10 13:36 ` sundeep subbaraya
2014-03-10 18:44 ` Felipe Balbi
2014-02-21 12:04 ` Mark Rutland
2014-02-21 13:41 ` Michal Simek
2014-02-21 13:57 ` Mark Rutland
2014-02-21 14:06 ` Michal Simek
2014-02-21 15:42 ` Felipe Balbi
2014-02-21 15:51 ` Michal Simek
2014-02-21 16:00 ` Felipe Balbi
2014-02-21 16:15 ` Arnd Bergmann
2014-02-21 15:41 ` Felipe Balbi
2014-02-21 16:13 ` Mark Rutland
2014-03-26 10:07 ` sundeep subbaraya
2014-04-15 17:18 ` Felipe Balbi
2014-04-15 17:55 ` Alan Stern
2014-04-16 4:39 ` Felipe Balbi
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=20150225220047.GS11136@saruman.tx.rr.com \
--to=balbi@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=monstr@monstr.eu \
--cc=pavel@denx.de \
--cc=sr@denx.de \
--cc=wd@denx.de \
/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
Powered by JetHome