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=-0.8 required=3.0 tests=DKIM_INVALID,DKIM_SIGNED, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, URIBL_BLOCKED autolearn=ham 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 61311C282CE for ; Wed, 22 May 2019 15:03:11 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id C69C720879 for ; Wed, 22 May 2019 15:03:10 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="key not found in DNS" (0-bit key) header.d=jilayne.com header.i=@jilayne.com header.b="Hszw4lBO" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729690AbfEVPDK (ORCPT ); Wed, 22 May 2019 11:03:10 -0400 Received: from mx1-c1.supremebox.com ([198.23.53.215]:49084 "EHLO mx1.supremebox.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1729517AbfEVPDK (ORCPT ); Wed, 22 May 2019 11:03:10 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=jilayne.com ; s=default; h=To:References:Message-Id:Content-Transfer-Encoding:Cc:Date: In-Reply-To:From:Subject:Mime-Version:Content-Type:Sender:Reply-To:Content-ID :Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To: Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe :List-Post:List-Owner:List-Archive; bh=oOPmSZh/NzIuiBunkW0F80Wezy1IGYkV8RbA80uyWaw=; b=Hszw4lBOe8DmCbEZjlxUKjzNga KaxyqNQ6ocvqYhhK4cIaXNYnm1gpKIWIataMJs+nUTI+oDsQNzSI+GkbKDf4gWd1HvbdGt9nePqkk kBuuoyzQmB8b5yAeCxFYRdv6DQYif/V83yp31Ys4zKGF4C5bqlfYzg0PqhE/r7m4FsGM=; Received: from [67.164.173.226] (helo=[10.0.0.176]) by mx1.supremebox.com with esmtpa (Exim 4.89) (envelope-from ) id 1hTSlo-0008Mq-8c; Wed, 22 May 2019 15:03:08 +0000 Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\)) Subject: Re: clarification on -only and -or-later From: J Lovejoy In-Reply-To: <20190522140014.GA8996@kroah.com> Date: Wed, 22 May 2019 09:03:07 -0600 Cc: Allison Randal , linux-spdx@vger.kernel.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <13E71306-C67C-418B-AB71-2C926B3EA58E@jilayne.com> <20190521172435.aez323uuvjcghejd@ebb.org> <595412F8-2FA4-4898-8B98-0251D493CBDA@jilayne.com> <20190522132347.GC28920@kroah.com> <350495e0-12cb-ff16-69bd-94edf50db133@lohutok.net> <20190522140014.GA8996@kroah.com> To: Greg KH X-Mailer: Apple Mail (2.3445.104.11) X-Sender-Ident-agJab5osgicCis: opensource@jilayne.com Sender: linux-spdx-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-spdx@vger.kernel.org > On May 22, 2019, at 8:00 AM, Greg KH = wrote: >=20 > On Wed, May 22, 2019 at 09:53:48AM -0400, Allison Randal wrote: >> On 5/22/19 2:23 PM, Greg KH wrote: >>> On Tue, May 21, 2019 at 12:05:37PM -0600, J Lovejoy wrote: >>>>=20 >>>> I think what I was looking for here, was confirmation as to whether = we >>>> want to do the =E2=80=9Cliteral=E2=80=9D GPL-1.0-or-later option = that the license >>>> provides for, or trigger the option to =E2=80=9Cchoose any = version=E2=80=9D and go >>>> with GPL-2.0-or-later for consistency of v2 across the kernel and = for >>>> other reasons I believe you raised regarding GPL-1.0 >>>=20 >>> I don't understand. Can you point to any files in the kernel where = we >>> have used the "GPL-1.0+" marking incorrectly? >>=20 >> Jilayne's question wasn't about current usage in the kernel, it was >> about what we should do in this cleanup process when we get to files >> where the license notice doesn't have an explicit GPL version number = or >> include the "or later" text. Thomas hasn't gotten to those patterns = yet >> in his batch processing. >=20 > Ah, ok. >=20 > But note, we have already marked such files as "GPL-1.0+" in the past, > so any change in that behavior would require us go back and change = what > we did, showing the justification for that. >=20 > I would stick to the rule of what we have already done in these cases, > it's simpler and seems to make sense of a crazy situation. >=20 Thanks Allison for helping to clarify and yes, if there is a pattern = already, it=E2=80=99d be really helpful for someone to send me a few = examples. The examples you=E2=80=99ve seen already may not match some of the = =E2=80=9Cmessy files=E2=80=9D I=E2=80=99m looking at, but it=E2=80=99d = still be helpful. thanks, Jilayne