From: Dave Hansen <dave.hansen@intel.com>
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
Subject: Re: [PATCH] selftest/x86/meltdown: Add a selftest for meltdown
Date: Thu, 5 Jan 2023 07:26:13 -0800 [thread overview]
Message-ID: <8bbc881b-15ea-1c8a-43ad-423f5a014c99@intel.com> (raw)
In-Reply-To: <Y7bg5sxEZDIaGoXK@kroah.com>
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/
next prev parent reply other threads:[~2023-01-05 15:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-05 12:35 [PATCH] selftest/x86/meltdown: Add a selftest for meltdown Aaron Lu
2023-01-05 13:42 ` Greg KH
2023-01-05 14:11 ` Raphael S. Carvalho
2023-01-05 14:38 ` Greg KH
2023-01-05 15:26 ` Dave Hansen [this message]
2023-01-06 1:00 ` Aaron Lu
2023-01-07 8:18 ` Greg KH
2023-01-07 8:50 ` Pavel Boldin
2023-01-09 8:05 ` Aaron Lu
2023-01-18 5:20 ` Aaron Lu
2023-01-09 7:38 ` Aaron Lu
2023-01-18 5:22 ` Aaron Lu
2023-01-19 16:12 ` Greg KH
2023-01-20 2:14 ` Lu, Aaron
2023-01-19 17:15 ` Pavel Boldin
2023-01-20 2:10 ` Lu, Aaron
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8bbc881b-15ea-1c8a-43ad-423f5a014c99@intel.com \
--to=dave.hansen@intel.com \
--cc=aaron.lu@intel.com \
--cc=boldin.pavel@gmail.com \
--cc=daniel.gruss@iaik.tugraz.at \
--cc=github@mlq.me \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=michael.schwarz91@gmail.com \
--cc=pboldin@cloudlinux.com \
--cc=raphaelsc@scylladb.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox