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

On Fri, Nov 17, 2017 at 11:53:01AM +0100, Philippe Ombredanne wrote: > On Fri, Nov 17, 2017 at 9:57 AM, Greg Kroah-Hartman > wrote: > > On Fri, Nov 17, 2017 at 08:37:28AM +0100, Philippe Ombredanne wrote: > >> Or fix the non-standard redefinition of the MODULE_LICENSE

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

On Fri, Nov 17, 2017 at 11:53:01AM +0100, Philippe Ombredanne wrote: > On Fri, Nov 17, 2017 at 9:57 AM, Greg Kroah-Hartman > wrote: > > On Fri, Nov 17, 2017 at 08:37:28AM +0100, Philippe Ombredanne wrote: > >> Or fix the non-standard redefinition of the MODULE_LICENSE macro as > >> DRIVER_LICENSE

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

On Fri, Nov 17, 2017 at 9:57 AM, Greg Kroah-Hartman wrote: > On Fri, Nov 17, 2017 at 08:37:28AM +0100, Philippe Ombredanne wrote: >> Or fix the non-standard redefinition of the MODULE_LICENSE macro as >> DRIVER_LICENSE as in [2] and found elsewhere with >> grep -r .

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

On Fri, Nov 17, 2017 at 9:57 AM, Greg Kroah-Hartman wrote: > On Fri, Nov 17, 2017 at 08:37:28AM +0100, Philippe Ombredanne wrote: >> Or fix the non-standard redefinition of the MODULE_LICENSE macro as >> DRIVER_LICENSE as in [2] and found elsewhere with >> grep -r . -e "DRIVER_LICENSE" >> >>

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

On Fri, Nov 17, 2017 at 08:37:28AM +0100, Philippe Ombredanne wrote: > Or fix the non-standard redefinition of the MODULE_LICENSE macro as > DRIVER_LICENSE as in [2] and found elsewhere with > grep -r . -e "DRIVER_LICENSE" > > These break the otherwise nicely grepable MODULE_LICENSE macros >

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

On Fri, Nov 17, 2017 at 08:37:28AM +0100, Philippe Ombredanne wrote: > Or fix the non-standard redefinition of the MODULE_LICENSE macro as > DRIVER_LICENSE as in [2] and found elsewhere with > grep -r . -e "DRIVER_LICENSE" > > These break the otherwise nicely grepable MODULE_LICENSE macros >

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

On Thu, Nov 16, 2017 at 4:15 PM, Jonas Oberg wrote: > Hi, > >> One other thing that occurred to me is that documentation files, too, >> are copyrightable and should have license identifiers. > > Would it make sense to take an incremental approach to this? Get the > source code and

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

On Thu, Nov 16, 2017 at 4:15 PM, Jonas Oberg wrote: > Hi, > >> One other thing that occurred to me is that documentation files, too, >> are copyrightable and should have license identifiers. > > Would it make sense to take an incremental approach to this? Get the > source code and identifiers

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

On Thu, 16 Nov 2017, Jonas Oberg wrote: > > One other thing that occurred to me is that documentation files, too, > > are copyrightable and should have license identifiers. > > Would it make sense to take an incremental approach to this? Get the > source code and identifiers worked on by Thomas

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

On Thu, 16 Nov 2017, Jonas Oberg wrote: > > One other thing that occurred to me is that documentation files, too, > > are copyrightable and should have license identifiers. > > Would it make sense to take an incremental approach to this? Get the > source code and identifiers worked on by Thomas

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

Hi, > One other thing that occurred to me is that documentation files, too, > are copyrightable and should have license identifiers. Would it make sense to take an incremental approach to this? Get the source code and identifiers worked on by Thomas et al through first, then think about and fix

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

Hi, > One other thing that occurred to me is that documentation files, too, > are copyrightable and should have license identifiers. Would it make sense to take an incremental approach to this? Get the source code and identifiers worked on by Thomas et al through first, then think about and fix

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

On Sun, 12 Nov 2017 20:18:22 +0100 Thomas Gleixner wrote: > --- /dev/null > +++ b/Documentation/license-rules.rst > @@ -0,0 +1,310 @@ > +Linux kernel licensing rules > + > + > +The Linux Kernel is provided under the terms of the GNU General Public

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

On Sun, 12 Nov 2017 20:18:22 +0100 Thomas Gleixner wrote: > --- /dev/null > +++ b/Documentation/license-rules.rst > @@ -0,0 +1,310 @@ > +Linux kernel licensing rules > + > + > +The Linux Kernel is provided under the terms of the GNU General Public > +License version 2

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 wrote: > > +C source: // SPDX-License-Identifier: > > +C header: /* SPDX-License-Identifier: */ > > So I can't be the only person with nothing better to do than to

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 wrote: > > +C source: // SPDX-License-Identifier: > > +C header: /* SPDX-License-Identifier: */ > > So I can't be the only person with nothing better to do than to wonder why > source

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

On Sun, 12 Nov 2017 20:18:22 +0100 Thomas Gleixner wrote: > Add a file to the Documentation directory to describe how file licenses > should be described in all kernel files, using the SPDX identifier, as well > as where all licenses should be in the kernel source tree for

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

On Sun, 12 Nov 2017 20:18:22 +0100 Thomas Gleixner wrote: > Add a file to the Documentation directory to describe how file licenses > should be described in all kernel files, using the SPDX identifier, as well > as where all licenses should be in the kernel source tree for people to > refer to

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

On Sun, 12 Nov 2017, Joe Perches wrote: > On Sun, 2017-11-12 at 20:18 +0100, Thomas Gleixner wrote: > > Add a file to the Documentation directory to describe how file licenses > > should be described in all kernel files, using the SPDX identifier, as well > > as where all licenses should be in

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

On Sun, 12 Nov 2017, Joe Perches wrote: > On Sun, 2017-11-12 at 20:18 +0100, Thomas Gleixner wrote: > > Add a file to the Documentation directory to describe how file licenses > > should be described in all kernel files, using the SPDX identifier, as well > > as where all licenses should be in

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

On Sun, 2017-11-12 at 20:18 +0100, Thomas Gleixner wrote: > Add a file to the Documentation directory to describe how file licenses > should be described in all kernel files, using the SPDX identifier, as well > as where all licenses should be in the kernel source tree for people to > refer to

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

On Sun, 2017-11-12 at 20:18 +0100, Thomas Gleixner wrote: > Add a file to the Documentation directory to describe how file licenses > should be described in all kernel files, using the SPDX identifier, as well > as where all licenses should be in the kernel source tree for people to > refer to

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

Add a file to the Documentation directory to describe how file licenses should be described in all kernel files, using the SPDX identifier, as well as where all licenses should be in the kernel source tree for people to refer to (LICENSES/). Thanks to Kate, Philippe and Greg for review and

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

Add a file to the Documentation directory to describe how file licenses should be described in all kernel files, using the SPDX identifier, as well as where all licenses should be in the kernel source tree for people to refer to (LICENSES/). Thanks to Kate, Philippe and Greg for review and