linux-kernel - Re: [PATCH AUTOSEL 4.19 07/27] intel_th: Use the correct style for SPDX License Identifier

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 for Android: free password hash cracker in your pocket

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

Message-ID: <20190820193715.GR30205@sasha-vm>
Date:   Tue, 20 Aug 2019 15:37:15 -0400
From:   Sasha Levin <sashal@...nel.org>
To:     Joe Perches <joe@...ches.com>
Cc:     linux-kernel@...r.kernel.org, stable@...r.kernel.org,
        Nishad Kamdar <nishadkamdar@...il.com>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: Re: [PATCH AUTOSEL 4.19 07/27] intel_th: Use the correct style for
 SPDX License Identifier

On Tue, Aug 20, 2019 at 06:47:53AM -0700, Joe Perches wrote:
>On Tue, 2019-08-20 at 09:41 -0400, Sasha Levin wrote:
>> From: Nishad Kamdar <nishadkamdar@...il.com>
>>
>> [ Upstream commit fac7b714c514fcc555541e1d6450c694b0a5f8d3 ]
>>
>> This patch corrects the SPDX License Identifier style
>> in header files related to Drivers for Intel(R) Trace Hub
>> controller.
>> For C header files Documentation/process/license-rules.rst
>> mandates C-like comments (opposed to C source files where
>> C++ style should be used)
>
>Is there a reason to backport license header changes?
>
>I believe there is not.

There is not, I must have missed this one.

--
Thanks,
Sasha