linux-kernel - Re: [Pv-drivers] [PATCH 1/4] x86/vmware: Update platform detection code for VMCALL/VMMCALL hypercalls

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: <BD402DB5-8709-4D6B-BBBD-6406252441A7@vmware.com>
Date:   Tue, 20 Aug 2019 17:18:00 +0000
From:   Darren Hart <dvhart@...are.com>
To:     Thomas Gleixner <tglx@...utronix.de>
CC:     Thomas Hellström (VMware) 
        <thomas_os@...pmail.org>, Pv-drivers <Pv-drivers@...are.com>,
        "x86@...nel.org" <x86@...nel.org>,
        "Doug@...are.com" <Doug@...are.com>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        Doug Covelli <dcovelli@...are.com>,
        Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
        "H. Peter Anvin" <hpa@...or.com>
Subject: Re: [Pv-drivers] [PATCH 1/4] x86/vmware: Update platform detection
 code for VMCALL/VMMCALL hypercalls


> On Aug 18, 2019, at 12:20 PM, Thomas Gleixner <tglx@...utronix.de> wrote:
> 
> While at it could you please ask your legal folks whether that custom
> license boilerplate can go away as well?

If you’re referring to the GPL boilerplate with “no warranty" and physical
address, then yes, as a matter of best practice (at VMware), that can and
should all be removed when adding the SPDX identifier - and of course, as
you said, be done as a separate patch.

Thanks,

-- 
Darren Hart