From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.4 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id E52C7C43331 for ; Tue, 31 Mar 2020 12:52:25 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id B740A208E4 for ; Tue, 31 Mar 2020 12:52:25 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=ideasonboard.com header.i=@ideasonboard.com header.b="loJZXkzV" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730469AbgCaMwZ (ORCPT ); Tue, 31 Mar 2020 08:52:25 -0400 Received: from perceval.ideasonboard.com ([213.167.242.64]:32812 "EHLO perceval.ideasonboard.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730418AbgCaMwY (ORCPT ); Tue, 31 Mar 2020 08:52:24 -0400 Received: from pendragon.ideasonboard.com (81-175-216-236.bb.dnainternet.fi [81.175.216.236]) by perceval.ideasonboard.com (Postfix) with ESMTPSA id 4BB1CB18; Tue, 31 Mar 2020 14:52:22 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ideasonboard.com; s=mail; t=1585659142; bh=c14UmhR+VSQy+0YEeVT6dAmWibySUvRjSpEVBUh8h9o=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=loJZXkzVDFgHAy1+WDL2NuorSOCZZvZRHaOj+Mm58ctdxjNh1PExDJMCiwOXVF+DK xArIrighC6BlxUPY7e2AkLNSo5+qyFE2iNvy4Vr7Neyf93YOcsVDvEI46jX1oyrmox 1V7tYK7KnRmvInL3NhydHz3JGNFxOc7xlfeDpI1I= Date: Tue, 31 Mar 2020 15:52:16 +0300 From: Laurent Pinchart To: Greg Kroah-Hartman Cc: devel@driverdev.osuosl.org, Philipp Zabel , Mauro Carvalho Chehab , Chen-Yu Tsai , Maxime Ripard , linux-rockchip@lists.infradead.org, Helen Koike , Sakari Ailus , Ezequiel Garcia , linux-arm-kernel@lists.infradead.org, Linux Media Mailing List Subject: Re: [PATCH v4 17/33] media: add SPDX headers on Kconfig and Makefile files Message-ID: <20200331125216.GE4767@pendragon.ideasonboard.com> References: <981eea64742859c63d8ab88c24b1b3380ee32dd2.1585651678.git.mchehab+huawei@kernel.org> <20200331120608.GB4767@pendragon.ideasonboard.com> <20200331122209.GA1627483@kroah.com> <20200331123914.GC4767@pendragon.ideasonboard.com> <20200331124756.GA1634223@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20200331124756.GA1634223@kroah.com> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-media-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-media@vger.kernel.org Hi Greg, On Tue, Mar 31, 2020 at 02:47:56PM +0200, Greg Kroah-Hartman wrote: > On Tue, Mar 31, 2020 at 03:39:14PM +0300, Laurent Pinchart wrote: > > On Tue, Mar 31, 2020 at 02:22:09PM +0200, Greg Kroah-Hartman wrote: > > > On Tue, Mar 31, 2020 at 03:06:08PM +0300, Laurent Pinchart wrote: > > > > On Tue, Mar 31, 2020 at 01:11:53PM +0200, Mauro Carvalho Chehab wrote: > > > > > Most of media Kconfig/Makefile files already has SPDX, > > > > > but there are a few ones still missing. Add it to them. > > > > > > > > I think it's a good idea to state the license of each source file, the > > > > patch looks fine to me. I've however been thinking about licenses for > > > > build system files recently, and I'll hijack this thread a bit to ask a > > > > question :-) > > > > > > > > For a project like the Linux kernel, and especially for subsystems that > > > > are covered by a single license, the choice is easy, we can apply the > > > > same license to the build files. However, for a project that contains > > > > components covered by different licenses (such as, for instance, an LGPL > > > > library, a GPL application and a BSD plugin), how should the license > > > > covering the build system files be selected ? I searched a bit for > > > > guidance on this topic, and couldn't find much. > > > > > > By "default" if there is no license on a file in the kernel tree, it > > > falls under the GPLv2 license and we should explicity state it, like > > > this patch does. > > > > > > So this is fine, but if you want to license the build files some other > > > way, that's good too, but do so when you add them to the tree, not at > > > some later time when it could cause confusion :) > > > > Thanks for your answer. I was hijacking the thread a little bit, the > > question wasn't related to the kernel, but in this case to libcamera. > > We've been wondering how to pick licenses for build files there, and I > > thought fellow kernel developers may have valuable input on this topic. > > I would make the files the same license as your project overall is to > make things simpler for everyone involved :) I would if the project had a single license, but we have GPL, LGPL and BSD components :-S -- Regards, Laurent Pinchart