[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2023100458-confusing-carton-3302@gregkh>
Date: Wed, 4 Oct 2023 08:11:13 +0200
From: Greg KH <gregkh@...uxfoundation.org>
To: Wei Liu <wei.liu@...nel.org>
Cc: Nuno Das Neves <nunodasneves@...ux.microsoft.com>,
linux-hyperv@...r.kernel.org, linux-kernel@...r.kernel.org,
x86@...nel.org, linux-arm-kernel@...ts.infradead.org,
linux-arch@...r.kernel.org, patches@...ts.linux.dev,
mikelley@...rosoft.com, kys@...rosoft.com, haiyangz@...rosoft.com,
decui@...rosoft.com, apais@...ux.microsoft.com,
Tianyu.Lan@...rosoft.com, ssengar@...ux.microsoft.com,
mukeshrathor@...rosoft.com, stanislav.kinsburskiy@...il.com,
jinankjain@...ux.microsoft.com, vkuznets@...hat.com,
tglx@...utronix.de, mingo@...hat.com, bp@...en8.de,
dave.hansen@...ux.intel.com, hpa@...or.com, will@...nel.org,
catalin.marinas@....com
Subject: Re: [PATCH v4 13/15] uapi: hyperv: Add mshv driver headers defining
hypervisor ABIs
On Tue, Oct 03, 2023 at 11:29:42PM +0000, Wei Liu wrote:
> > > > > diff --git a/include/uapi/hyperv/hvgdk.h b/include/uapi/hyperv/hvgdk.h
> > > > > new file mode 100644
> > > > > index 000000000000..9bcbb7d902b2
> > > > > --- /dev/null
> > > > > +++ b/include/uapi/hyperv/hvgdk.h
> > > > > @@ -0,0 +1,41 @@
> > > > > +/* SPDX-License-Identifier: MIT */
> > > >
> > > > That's usually not a good license for a new uapi .h file, why did you
> > > > choose this one?
> > > >
> > >
> > > This is chosen so that other Microsoft developers who don't normally
> > > work on Linux can review this code.
> >
> > Sorry, but that's not how kernel development is done. Please fix your
> > internal review processes and use the correct uapi header file license.
> >
> > If your lawyers insist on this license, that's fine, but please have
> > them provide a signed-off-by on the patch that adds it and have it
> > documented why it is this license in the changelog AND in a comment in
> > the file so we can understand what is going on with it.
> >
>
> We went through an internal review with our legal counsel regarding the
> MIT license. We have an approval from them.
>
> Let me ask if using something like "GPL-2.0 WITH Linux-syscall-note OR
> MIT" is possible.
That marking makes no sense from a legal point of view, please work with
your lawyers as it seems they do not understand license descriptions
very well :(
thanks,
greg k-h
Powered by blists - more mailing lists