Received: by 2002:a25:c593:0:0:0:0:0 with SMTP id v141csp3031094ybe; Sun, 8 Sep 2019 05:48:38 -0700 (PDT) X-Google-Smtp-Source: APXvYqwaxMCcOTNOUYwXGXYaweqrvCwXr/xWgGXTKkCoaOOSusRYe0y6Yez6SbVuHxI0JKfRZ5CL X-Received: by 2002:a05:6402:134d:: with SMTP id y13mr18722045edw.209.1567946918164; Sun, 08 Sep 2019 05:48:38 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1567946918; cv=none; d=google.com; s=arc-20160816; b=0hk8918qv+WRpvEpsP3j+P3cBSG+oaIC0AeTTV4qUzfvJ2DdNnKhvZDN8ppKCBr+Lb 15SdlH+xCLgVTSdtcdKSeupYBSociIHKrjYmMen1xloG0hfyZE5tMbFxgNG7kPfsw0l7 M7SPjuTFHowwIeIGxfjeTvrxho939PH364oi3qV32B2dvesXLFcZ8jymCxIERdknBigi fRbDJHrsIg8Y7tJNbVrnC/4alftWc6aJrxoeg/R2MHtByd8S8wfLSfxxBBd4pEp1F1K/ OByDksO56iyTTAOxHaOMq91eLYBD1fwpLx/iUM5YpQnudZWtFz6Oje9T69dkdwXyZA3X w+Zg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :organization:references:in-reply-to:message-id:subject:cc:to:from :date; bh=Em8ki0pDAbN1kTXoBiDpcCPVlBh5qtHdj020wAW2daw=; b=XF6e7QyLxKhZsY5x+2MES5Su91h2OZbaJaVMPNullYV80UIoTNXT+a+7fV2C3ktS7y +0VHldg3q/AKoSu26MCo4V9GbXDeZ1C34moMbetAvYijxB+xfCoXf5IP0oL5YWMT1Vuv XJ21pjiMUckgClbKVkWLerPDvQSvwaROkloJCs0pHHZXWJYF3dBWXY9HQKDqxEO1STC3 CH9K3X/YrbRE4dHJGljTbBKns+1go9VqSPi434BxABqq6NfPE5ZMosZyH9iqvG8kssRB ZItDGZW9IcXOwNpTVxG25TSbdhibOPuWu9JqjN6kGp+BFvU0DT/4qIkN2GbfRK656Q+c donA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id k55si7441065edd.179.2019.09.08.05.48.14; Sun, 08 Sep 2019 05:48:38 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2393131AbfIGNeW (ORCPT + 99 others); Sat, 7 Sep 2019 09:34:22 -0400 Received: from ms.lwn.net ([45.79.88.28]:42594 "EHLO ms.lwn.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1731344AbfIGNeW (ORCPT ); Sat, 7 Sep 2019 09:34:22 -0400 Received: from lwn.net (localhost [127.0.0.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ms.lwn.net (Postfix) with ESMTPSA id 6B6A82BD; Sat, 7 Sep 2019 13:34:20 +0000 (UTC) Date: Sat, 7 Sep 2019 07:34:19 -0600 From: Jonathan Corbet To: Mauro Carvalho Chehab Cc: Linux Media Mailing List , Mauro Carvalho Chehab , Greg Kroah-Hartman , Joe Perches , linux-kernel@vger.kernel.org, Arnaldo Carvalho de Melo , Sven Eckelmann , Ingo Molnar , Thomas Gleixner , Doug Smythies , =?UTF-8?B?QXVyw6lsaWVu?= Cedeyn , Vincenzo Frascino , linux-doc@vger.kernel.org, "Rafael J. Wysocki" , Andrew Morton , Thierry Reding , Armijn Hemel , Jiri Olsa , Uwe =?UTF-8?B?S2xlaW5lLUvDtm5pZw==?= , Namhyung Kim , Peter Zijlstra , Federico Vaga , Allison Randal , Alexander Shishkin Subject: Re: [PATCH 0/6] Address issues with SPDX requirements and PEP-263 Message-ID: <20190907073419.6a88e318@lwn.net> In-Reply-To: References: Organization: LWN.net MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 5 Sep 2019 16:57:47 -0300 Mauro Carvalho Chehab wrote: > The description at Documentation/process/license-rules.rst is very strict > with regards to the position where the SPDX tags should be. > > In the past several developers and maintainers interpreted it on a > more permissive way, placing the SPDX header between lines 1 to 15, > with are the ones which the scripts/spdxcheck.py script verifies. > > However, recently, devs are becoming more strict about such > requirement and want it to strictly follow the rule, with states that > the SPDX rule should be at the first line ever on most files, and > at the second line for scripts. > > Well, for Python script, such requirement causes violation to PEP-263, > making regressions on scripts that contain encoding lines, as PEP-263 > also states about the same. > > This series addresses it. So I really don't want to be overly difficult here, but I would like to approach this from yet another angle... > Patches 1 to 3 fix some Python scripts that violates PEP-263; I just checked all of those scripts, and they are all just plain ASCII. So it really doesn't matter whether the environment defaults to UTF-8 or ASCII here. So, in other words, we really shouldn't need to define the encoding at all. This suggests to me that we're adding a bunch of complications that we don't necessarily need. What am I missing here? Educate me properly and I'll not try to stand in the way of all this... Thanks, jon