From: Greg KH <gregkh@linuxfoundation.org>
To: Dave Hansen <dave.hansen@intel.com>
Cc: Aaron Lu <aaron.lu@intel.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
Tony Luck <tony.luck@intel.com>,
"Yin, Fengwei" <fengwei.yin@intel.com>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
"Huang, Ying" <ying.huang@intel.com>,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH v3] selftest/x86/meltdown: Add a selftest for meltdown
Date: Thu, 17 Nov 2022 07:10:44 +0100 [thread overview]
Message-ID: <Y3XQZFyiXYc9mJ1Y@kroah.com> (raw)
In-Reply-To: <f8c3da3a-4d19-60c6-66d3-afd0d56ef102@intel.com>
On Wed, Nov 16, 2022 at 02:57:22PM -0800, Dave Hansen wrote:
> On 11/14/22 22:54, Greg KH wrote:
> > On Tue, Nov 15, 2022 at 10:15:03AM +0800, Aaron Lu wrote:
> >> I came to the conclusion that this work is OK to submit with all of the
> >> steps I listed above (copyright notices, license terms and relicensing)
> >> by strictly following all of the processes required by my employer.
> >>
> >> This does not include a Signed-off-by from a corporate attorney.
> > Please get that, as that is what I asked for in order for us to be able
> > to accept this type of change.
>
> Hi Greg,
>
> Can you share any more of what triggered this new requirement?
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.
This isn't a new type of requirement, I make this request to many other
companies that do things that are not "normal" when it comes to licenses
and copyrights so as to ensure that all is ok.
thanks,
greg k-h
next prev parent reply other threads:[~2022-11-17 6:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-15 2:15 [RFC PATCH v3] selftest/x86/meltdown: Add a selftest for meltdown Aaron Lu
2022-11-15 6:54 ` Greg KH
2022-11-16 22:57 ` Dave Hansen
2022-11-17 6:10 ` Greg KH [this message]
2022-11-17 18:43 ` Dave Hansen
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=Y3XQZFyiXYc9mJ1Y@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=aaron.lu@intel.com \
--cc=dave.hansen@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=fengwei.yin@intel.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=tony.luck@intel.com \
--cc=ying.huang@intel.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