linux-kernel - Re: SPDX-License-Identifier

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 2 Feb 2015 08:06:22 -0800
From:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:	Stefan Roese <sr@...x.de>
Cc:	monstr@...str.eu, balbi@...com, linux-kernel@...r.kernel.org,
	devicetree@...r.kernel.org, Wolfgang Denk <wd@...x.de>
Subject: Re: SPDX-License-Identifier

On Mon, Feb 02, 2015 at 04:43:14PM +0100, Stefan Roese wrote:
> On 21.02.2014 17:18, Michal Simek wrote:
> >On 02/21/2014 05:12 PM, Felipe Balbi wrote:
> >>On Fri, Feb 21, 2014 at 05:04:26PM +0100, Michal Simek wrote:
> >>>On 02/21/2014 05:04 PM, Greg Kroah-Hartman wrote:
> >>>>On Fri, Feb 21, 2014 at 07:38:16AM +0100, Michal Simek wrote:
> >>>>>BTW: u-boot started to use SPDX-License-Identifier
> >>>>>which will be nice to start to use.
> >>>>
> >>>>I agree, feel free to start sending patches to use this type of
> >>>>identifier for drivers.
> >>>
> >>>But we probably need to add that Licenses to one location.
> >>>Documentation/Licenses?
> >>
> >>Just add to the drivers themselves, just like u-boot is doing. A simple:
> >>
> >>	$ git grep -e SPDX-License-Identifier
> >>
> >>will tell you filename and license. Or did I misunderstand your question ?
> >
> >But for doing this it is probably necessary to have location where
> >you will place that licenses and you will explain what it is how
> >it is done by Wolfgang in this commit.
> >
> >http://git.denx.de/?p=u-boot.git;a=commitdiff;h=eca3aeb352c964bdb28b8e191d6326370245e03f
> >
> >Then yes, adding one line is enough.
> I would like to revive this thread regarding SPDX license identifiers in the
> Linux kernel. And check how to best start / proceed with the integration
> now.

Why do you want to do this?

> Greg, if you are open to patches adding this one-line SPDX license tag to
> the source code, how should I begin with such a task in your opinion? Should
> I add those tags for just one driver directory (e.g. drivers/base/*) first?
> And send those patches to the list(s) for review. Or do you have other
> suggestions on how to start with this task?

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.

thanks,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/