linux-kernel - Re: [PATCH v2 3/5] ASoC: max9860: switch to SPDX license tag

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20180416113535.GA20726@sirena.org.uk>
Date:   Mon, 16 Apr 2018 12:35:35 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Christoph Hellwig <hch@...radead.org>
Cc:     Peter Rosin <peda@...ntia.se>, linux-kernel@...r.kernel.org,
        Liam Girdwood <lgirdwood@...il.com>,
        Jaroslav Kysela <perex@...ex.cz>,
        Takashi Iwai <tiwai@...e.com>, alsa-devel@...a-project.org
Subject: Re: [PATCH v2 3/5] ASoC: max9860: switch to SPDX license tag

On Sun, Apr 15, 2018 at 12:32:29AM -0700, Christoph Hellwig wrote:
> On Fri, Apr 13, 2018 at 12:19:27PM +0100, Mark Brown wrote:
> > On Thu, Apr 12, 2018 at 11:14:35PM +0200, Peter Rosin wrote:

> > > @@ -1,3 +1,4 @@
> > > +// SPDX-License-Identifier: GPL-2.0
> > >  /*
> > >   * Driver for the MAX9860 Mono Audio Voice Codec
> > >   *

> > Please don't mix C and C++ comments like this - it looks unintentional
> > and messy.  Just convert the entire comment block to C++ so it's
> > consistent with itself.

> NAK - that is exactky the wrong way to go.  Normal Linux comments are
> classi C-style comments and should remain so.  SPDX tags use c++
> comments exactly to be different and stick out.

During some of the discussions of the SPDX stuff Linus was expressing a
willingness or desire to just use C++ comments where sensible outside of
the SPDX headers, especially with single line stuff though this seems
like another useful exception.

Quite why we'd particularly need to have the SPDX stuff sticking out
isn't really obvious either; there's the desire to have something very
consistent to ease machine parsing but it's not exactly what I'd expect
most humans to be first looking for when they open a source file.

Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)