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=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS 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 AB2CCC4321B for ; Tue, 11 Jun 2019 14:19:15 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 83F5F20896 for ; Tue, 11 Jun 2019 14:19:15 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2388411AbfFKOTP (ORCPT ); Tue, 11 Jun 2019 10:19:15 -0400 Received: from Galois.linutronix.de ([146.0.238.70]:58305 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2387551AbfFKOTO (ORCPT ); Tue, 11 Jun 2019 10:19:14 -0400 Received: from [5.158.153.52] (helo=nanos.tec.linutronix.de) by Galois.linutronix.de with esmtpsa (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1hahcE-0004da-Rz; Tue, 11 Jun 2019 16:19:11 +0200 Date: Tue, 11 Jun 2019 16:19:10 +0200 (CEST) From: Thomas Gleixner To: "Enrico Weigelt, metux IT consult" cc: Richard Fontana , Greg KH , Philippe Ombredanne , linux-spdx@vger.kernel.org Subject: Re: [Batch 17 patch 43/57] treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 494 In-Reply-To: Message-ID: References: <20190604081044.651381636@linutronix.de> <20190604081206.123876666@linutronix.de> <1199b8ef-01e5-aa72-9673-f38b05434d14@metux.net> <20190610154555.GA28774@kroah.com> User-Agent: Alpine 2.21 (DEB 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: linux-spdx-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-spdx@vger.kernel.org Enrico, On Tue, 11 Jun 2019, Enrico Weigelt, metux IT consult wrote: > On 10.06.19 18:49, Richard Fontana wrote: > > > > Befeore spending more time w/ guessing, why not just > ask the authors ? First of all this is not about guessing. We are analysing the existing notice/reference and build up reasonable argumentation for coming to a conclusion. Secondly, as I told you in a previous reply in this very same thread, the authorship is unclear as the code and the notice goes back to 2.3.17, i.e. Sept. 1999. I've already did the detective work to figure out who the original author is and where he's reachable. I just did not come around to contact him because I took the liberty to take a few days off. Thanks, tglx