linux-kernel - Re: [PATCH] platform/x86: dell-rbtn: Block comments use * on subsequent lines

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: <BM1PR0101MB14445D796D67A2A4C0C002B4E60A0@BM1PR0101MB1444.INDPRD01.PROD.OUTLOOK.COM>
Date:   Thu, 14 Dec 2017 09:12:06 +0000
From:   Dhaval Shah <dhaval.shah@...tnautics.com>
To:     Joe Perches <joe@...ches.com>,
        Philippe Ombredanne <pombredanne@...b.com>
CC:     "pali.rohar@...il.com" <pali.rohar@...il.com>,
        Darren Hart <dvhart@...radead.org>,
        Andy Shevchenko <andy@...radead.org>,
        "platform-driver-x86@...r.kernel.org" 
        <platform-driver-x86@...r.kernel.org>,
        LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] platform/x86: dell-rbtn: Block comments use * on
 subsequent lines

________________________________________
> From: Joe Perches <joe@...ches.com>
> Sent: Wednesday, December 13, 2017 9:09 PM
> To: Dhaval Shah; Philippe Ombredanne
> Cc: pali.rohar@...il.com; Darren Hart; Andy Shevchenko; platform-driver-x86@...r.kernel.org; LKML
> Subject: Re: [PATCH] platform/x86: dell-rbtn: Block comments use * on subsequent lines
> 
> On Wed, 2017-12-13 at 12:41 +0000, Dhaval Shah wrote:
> > > If anyone does conversions of these license texts
> > > you have to be _extremely_ careful about what
> > > specific license identifier you use.
> > > This license includes the text
> > >         "or (at your option) any later version"
> > > which is not the same as using
> > >         SPDX-License-Identifier: GPL-2.0
> >
> > I have given this SPDX ID based on the current license info in the driver.
> 
> No, you have not.
> You have done it incorrectly.
> 
> For a short description, read:
> https://spdx.org/sites/cpstandard/files/pages/files/using_spdx_license_list_short_identifiers.pdf
> page 5
I got your point. SPDX text should be "SPDX-License-Identifier: GPL-2.0+".
Am i Right?