linux-kernel - Re: [PATCH 0/2] SPDX tags for copyright

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 for Android: free password hash cracker in your pocket

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

Message-ID: <YyAPsqKNSwdHccLj@infradead.org>
Date:   Mon, 12 Sep 2022 22:05:54 -0700
From:   Christoph Hellwig <hch@...radead.org>
To:     Uwe Kleine-König 
        <u.kleine-koenig@...gutronix.de>
Cc:     linux-kernel@...r.kernel.org,
        Kai Germaschewski <kai.germaschewski@....de>,
        Masahiro Yamada <masahiroy@...nel.org>,
        Marc Zyngier <maz@...nel.org>, kernel@...gutronix.de,
        linux-spdx@...r.kernel.org,
        Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [PATCH 0/2] SPDX tags for copyright

On Fri, Sep 09, 2022 at 12:38:48AM +0200, Uwe Kleine-König wrote:
> Hello,
> 
> for Debian packaging having SPDX license tags already simplifies
> creating the required copyright documentation considerably. Another
> information that is needed for Debian packaging is the copyright
> information. There is an SPDX way for copyright information, too. The
> second patch converts scripts/kallsyms.c to that mechanism as an example
> to maybe discuss if we want to do that in the kernel.
> 
> While the SPDX-FileCopyrightText is officially a free-form field, I
> suggest to just stick to the format
> 
> 	(<year> )?<copyright holder>
> 
> to simplify machine consumption even further.

Adding the linux-spdx list and Linus.  If we go with this format
(which doesn't sound bad), we'll clearly need to document the format
we want, and that people should use it.