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]
Date:   Sun, 31 Dec 2017 14:54:07 +0100
From:   Philippe Ombredanne <>
To:     Jiaxun Yang <>
Cc:     Ralf Baechle <>,
        Linux MIPS <>,
        LKML <>,
        Huacai Chen <>
Subject: Re: [PATCHv2 1/8] MIPS: Loongson64: cleanup all cs5536 files to use
 SPDX Identifier

On Sun, Dec 31, 2017 at 2:14 PM, Jiaxun Yang <> wrote:
> On 2017-12-31 Sun 12:17 +0100,Philippe Ombredanne wrote:
>> Did you CC the original authors? You would need their signoff or at
>> least an ack IMHO
> Yeah, I CC Huacai Chen in v1 as the Lemote staff who in charge of
> Loongson's mainline kernel. Can he sign-off for all the original
> authors who were from ICT and Lemote?
> As far as I know, some authors are no longer working in Lemote. And I
> can't see their new email addresses so it may hard to get their ack or
> sign-off.
> Thanks for your adivce.
> --
> Best Regards
> Jiaxun Yang

It would best if you can get all acks, at least one authoritative from
each org involved or from each individual involved if not part of an
org. I reckon it may be difficult. But then you can document with your
patch set who you contacted, who you got ack from and who you did not.

Then again you are not changing anything about the licensing: just
replacing licensing by value (e.g. a full notice) by a license by
reference (e.g. an SPDX tag that references the full text).

Philippe Ombredanne

Powered by blists - more mailing lists