linux-kernel - Re: [patch 1/7] Documentation: Add license-rules.rst to describe how to properly identify file licenses

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:   Sun, 12 Nov 2017 21:19:55 +0100 (CET)
From:   Thomas Gleixner <tglx@...utronix.de>
To:     Jonathan Corbet <corbet@....net>
cc:     LKML <linux-kernel@...r.kernel.org>,
        Linus Torvalds <torvalds@...uxfoundation.org>,
        Andrew Morton <akpm@...uxfoundation.org>,
        Philippe Ombredanne <pombredanne@...b.com>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Christoph Hellwig <hch@....de>,
        Russell King <rmk+kernel@...linux.org.uk>,
        Rob Herring <rob.herring@...aro.org>,
        Jonas Oberg <jonas@...e.org>, Joe Perches <joe@...ches.com>,
        linux-xfs@...r.kernel.org,
        Kate Stewart <kstewart@...uxfoundation.org>
Subject: Re: [patch 1/7] Documentation: Add license-rules.rst to describe
 how to properly identify file licenses

On Sun, 12 Nov 2017, Jonathan Corbet wrote:
> On Sun, 12 Nov 2017 20:18:22 +0100
> Thomas Gleixner <tglx@...utronix.de> wrote:
> > +    C source:   // SPDX-License-Identifier: <SPDX License Expression>
> > +    C header:   /* SPDX-License-Identifier: <SPDX License Expression> */
> 
> So I can't be the only person with nothing better to do than to wonder why
> source and header files use a different comment syntax.  Maybe the document
> could explain that?

Will do. The reason is that some build steps, one of them related to
generated .lds files fail with C++ style comments. Linus fixed the .lds
one, but there is at least an older ASM tool which doesn't like them.

> > +    ASM:        /* SPDX-License-Identifier: <SPDX License Expression> */
> > +OR should be used if the file is dual licensed and only one license is
> > +to be selected.  For example, some dtsi files are available under dual
> > +licenses:
> 
> It would be good to document the set of permissible WITH exceptions.  Or
> people will surely get creative in making up new ones.
>
> 
> OK, I see that has been done, so amend that comment to suggest a line
> saying that the set of exceptions is documented below.

Will do. The other thing is, that the exception files have the applicable
licenses in it so something like checkpatch.pl can verify it.

Thanks,

	tglx