linux-kernel - Re: [patch V3 01/11] 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 for Android: free password hash cracker in your pocket

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

Message-ID: <20171117153847.251e578d@lwn.net>
Date:   Fri, 17 Nov 2017 15:38:47 -0700
From:   Jonathan Corbet <corbet@....net>
To:     Thomas Gleixner <tglx@...utronix.de>
Cc:     LKML <linux-kernel@...r.kernel.org>,
        Linus Torvalds <torvalds@...uxfoundation.org>,
        Andrew Morton <akpm@...uxfoundation.org>,
        Kate Stewart <kstewart@...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,
        Charlemagne Lasse <charlemagnelasse@...il.com>,
        Carmen Bianca Bakker <carmenbianca@...e.org>
Subject: Re: [patch V3 01/11] Documentation: Add license-rules.rst to
 describe how to properly identify file licenses

On Fri, 17 Nov 2017 10:48:57 +0100 (CET)
Thomas Gleixner <tglx@...utronix.de> wrote:

> > > +The following describes the license of the Linux kernel source code
> > > +(GPLv2), how to properly mark the license of individual files in the source
> > > +tree, as well as links to the full license text.
> > > +
> > > +.. toctree::
> > > +   :maxdepth: 2
> > > +
> > > +   process/license-rules.rst
> > > +  
> > 
> > I'll confess that I'm not convinced that information on license identifiers
> > is the very first thing readers should encounter when entering the kernel's
> > documentation.  But I'll not quibble about it for now, we can always move
> > it later :)  
> 
> Any suggestions for a better place?

I'd put it into Documentation/process/index.rst.  That is where we have
put the rest of that kind of information - stuff that people who want to
do kernel development need to know.

Other than that quibble, V4 looks good to me; toss in a

	Reviewed-by: Jonathan Corbet <corbet@....net>

if you like.

Thanks,

jon