From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751482AbdKVNXc (ORCPT ); Wed, 22 Nov 2017 08:23:32 -0500 Received: from verein.lst.de ([213.95.11.211]:44417 "EHLO newverein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751260AbdKVNXb (ORCPT ); Wed, 22 Nov 2017 08:23:31 -0500 Date: Wed, 22 Nov 2017 14:23:29 +0100 From: Christoph Hellwig To: Mauro Carvalho Chehab Cc: Thomas Gleixner , Christoph Hellwig , LKML , Linus Torvalds , Andrew Morton , Jonathan Corbet , Kate Stewart , Philippe Ombredanne , Greg Kroah-Hartman , Russell King , Rob Herring , Jonas Oberg , Joe Perches , linux-xfs@vger.kernel.org, Charlemagne Lasse , Carmen Bianca Bakker Subject: Re: [patch V4 01/11] Documentation: Add license-rules.rst to describe how to properly identify file licenses Message-ID: <20171122132328.GA26023@lst.de> References: <20171116183306.103584007@linutronix.de> <20171116184358.398030394@linutronix.de> <20171117150639.0e706421@vento.lan> <20171117183946.GA28533@lst.de> <20171122095117.49c558a4@vento.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20171122095117.49c558a4@vento.lan> User-Agent: Mutt/1.5.17 (2007-11-01) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Nov 22, 2017 at 09:51:17AM -0200, Mauro Carvalho Chehab wrote: > Also, one may forget that headers use /**/ and end by doing the wrong > thing, as a common practice is to just cut-and-paste the same copyright > header on both C and H files at development time. Yes. > Make headers_install could replace such macros by SPDX comments when > installing on userspace. Agreed. Or for that matter we could simply stick to the comment version for UAPI headers only, and have a macro for everything else. > > - Breaks in assembly, boot and other special source files. There was no > > easy solution to that and the result would have been to have macros in > > some files and not in others. > > At the end, we have different markups, depending on the file type. > I guess the main problem of using a macro is that a module composed > by multiple C files will end by defining it multiple times. Not sure > if gcc would do the right thing on grouping everything altogether > and producing the right equivalent to MODULE_LICENSE(). We'd basically need to add a new entry to a section, similar to how say __setup works in the core kernel. But I think the important bit is to start with a macro now, even if it has zero functionality to start with - at least that enables us to fill the functionality once needed. > Also, at least on media, I found cases where the same module > has multiple licenses, e. g. some files that are grouped together on > a module are GPL v2 only, while others are GPL v2+. A module always has the least permissive license of all files.