Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp974380yba; Thu, 16 May 2019 11:59:19 -0700 (PDT) X-Google-Smtp-Source: APXvYqzLL1H60XL5xYVIT+htwfbk5daGcVpX+B9/cPGZx67fCE6XNYAuYhNgARBTOyGvckrQy8MS X-Received: by 2002:a65:6494:: with SMTP id e20mr43378935pgv.117.1558033159739; Thu, 16 May 2019 11:59:19 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1558033159; cv=none; d=google.com; s=arc-20160816; b=mWT0HPPNM7mGoCB7ujL5SQflXJs81RubfThBe9tqxb0aU/MN+uGJydmiWFb8Se1wMe DYqiSOQXTayRuQ6hY9+Uu6eOnX7gKFlyNq9E07chAI42hQy/Td7GMlMEQTtgIw68UN+/ eFDbo8RVCCeB3HgiSOit/kTOPsLSGTC3psps9XP1nfyQwSfuOoKJU7rpyoJKY8HJuEr6 fy8lDtvHkmcPQXl4D7n9QByJ5DrwKWjwERgvEAAdpA1fOAqzD85OJDKuSEjmMJRXjCuU Rj9Oj7UMNg3zQYrc3XjFyN7cnfV4+vb2Ah5k9VWEqxi/a9KgexO4SY/L0GG4NaGb2oPS BZQw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:user-agent:references :message-id:in-reply-to:subject:cc:to:from:date; bh=shDg5jTnC0KGw94L10epTbCmC1CFPZPAwXEirTKoPe0=; b=Y0ZSBCnUBEBme3soCHBpp1oNkwyY1I2bzwrnaIizHQPMFHWpIcCqYZyZUQ/q9OItSw NWkmfUbxwYNaJ3C0lC6+IPdfZDifLscrmQHXm563oa9BXGVPmAosfC6ygBpTBSjV2zOu 4yVvmfc2z+H746jzXokcy4pC1ZwWC5FX6sREIUSE8DyP1r9YvR14+nKNLiAlUM0255AE KBr5022Yzsg1SNjyHevJ8p2wwIE37AGSsUdP3QKSys4OVRb5vomOCdeDLI6Jgr5A9yLE LYt0QM7gOyU8KkaY/syy97GTWg8ew+vMM4Zu9sEtpnNZY/XO5mVDjUZPfWeYMNuCzwBW m35g== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-wireless-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-wireless-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 d125si6875820pfd.257.2019.05.16.11.58.58; Thu, 16 May 2019 11:59:19 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-wireless-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-wireless-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727086AbfEPSRL (ORCPT + 99 others); Thu, 16 May 2019 14:17:11 -0400 Received: from Galois.linutronix.de ([146.0.238.70]:48833 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726645AbfEPSRL (ORCPT ); Thu, 16 May 2019 14:17:11 -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 1hRKwG-0002vV-Kj; Thu, 16 May 2019 20:17:09 +0200 Date: Thu, 16 May 2019 20:17:08 +0200 (CEST) From: Thomas Gleixner To: Arend Van Spriel cc: Kalle Valo , linux-wireless Subject: Re: SPDX identifier In-Reply-To: Message-ID: References: User-Agent: Alpine 2.21 (DEB 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: linux-wireless-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-wireless@vger.kernel.org Arend, On Thu, 16 May 2019, Arend Van Spriel wrote: > Hi Kalle, Thomas, > > I added SPDX tags in brcm80211 driver sources. Although it is a no-brainer I > decided to run checkpatch for the changes and quirky stuff started to happen. > For all files I added: > > // SPDX-License-Identifier > > but checkpatch started complaining I should use /* ... */ instead of //. > > WARNING: Improper SPDX comment style for > 'drivers/net/wireless/broadcom/brcm80211/include/brcm_hw_ids.h', please use > '/*' instead > #29: FILE: drivers/net/wireless/broadcom/brcm80211/include/brcm_hw_ids.h:1: > +// SPDX-License-Identifier: ISC > > So I edited all patches and ran again. And again it started complaining. > > WARNING: Improper SPDX comment style for > 'drivers/net/wireless/broadcom/brcm80211/brcmsmac/aiutils.c', please use '//' > instead > > So now I am in a bonkers state. It seems for header files we want /* */ and > for c files we want //. For real? See Documentation. This is historical because the older binutils choked on '//' comments. Not longer an issue as we moved to more modern binutils by now. So we can fixup the documentation and allow // style for headers as well. Thanks, tglx