Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Message-ID: <8bbc881b-15ea-1c8a-43ad-423f5a014c99@intel.com>
Date:   Thu, 5 Jan 2023 07:26:13 -0800
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101
 Thunderbird/102.6.1
Subject: Re: [PATCH] selftest/x86/meltdown: Add a selftest for meltdown
Content-Language: en-US
To:     Greg KH <gregkh@linuxfoundation.org>,
        "Raphael S. Carvalho" <raphaelsc@scylladb.com>
Cc:     Aaron Lu <aaron.lu@intel.com>,
        Pavel Boldin <pboldin@cloudlinux.com>,
        Pavel Boldin <boldin.pavel@gmail.com>,
        Moritz Lipp <github@mlq.me>,
        Daniel Gruss <daniel.gruss@iaik.tugraz.at>,
        Michael Schwarz <michael.schwarz91@gmail.com>,
        linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
References: <Y7bD+R/cxZ4p/nWe@ziqianlu-desk1> <Y7bT0OL8RAWkCu0Z@kroah.com>
 <CAKhLTr1a+fTs2KyT3fm9yMxfjNwW_yLV7vRjrUXdNx8gfg8LqA@mail.gmail.com>
 <Y7bg5sxEZDIaGoXK@kroah.com>
From:   Dave Hansen <dave.hansen@intel.com>
In-Reply-To: <Y7bg5sxEZDIaGoXK@kroah.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: bulk

On 1/5/23 06:38, Greg KH wrote:
> But hey, what do I know, I'm not a lawyer which is why I keep insisting
> that one from Intel actually read over this submission and sign-off on
> it to verify that they agree with all of this.

I guess I'm still confused what is triggering the lawyer requirement.
Last time, you asked:

> You are taking source from a non-Intel developer under a different
> license and adding copyright and different license information to it.
> Because of all of that, I have the requirement that I want to know that
> Intel legal has vetted all of this and agrees with the conclusions that
> you all are stating.

To break that down, the earlier submission[1] had:

 * Original developer from a different company
 * Non-GPL original license
 * Relicensing
 * Addition of a new copyright

I can see all of those thing adding up together to trigger the higher
bar of having a lawyer sign off.  It looks like Aaron took that issue
list and tried to improve on it.  This new submission has:

 * Original developer from a different company

Is there anything else in this submission which is triggering the lawyer
review requirement?

If not, I'd be happy to hack up a Documentation patch to describe this
review requirement and make it clear to everyone.  I've gotten traction
with my colleagues in the past once things were fully and clearly
documented.  I'm hoping history repeats itself here.

1. https://lore.kernel.org/all/Y3L2Jx3Kx9q8Dv55@ziqianlu-desk1/