Re: [PATCH v2] misc: hpilo: relicense HPE iLO driver as Dual MIT/GPL

[Greg KH]

On Thu, Feb 09, 2023 at 03:59:04AM +0000, Gaba, Aahit wrote:
> On Thu, Feb 09, 2023 at 09:29:00AM +0530, Aahit Gaba wrote:
> > On Wed, Nov 16, 2022 at 12:36:40PM +0100, Greg KH wrote:
> > > On Wed, Nov 16, 2022 at 06:34:57PM +0800, matt.hsiao@xxxxxxx wrote:
> > > > From: Matt Hsiao <matt.hsiao@xxxxxxx>
> > > >
> > > > Currently, the hpilo driver is licensed as GPL. To run OpenBSD on
> > > > HPE servers with BMC (HPE iLO) functionality, a dual MIT/GPL license
> > > > is needed for porting the hpilo driver to OpenBSD.
> > > >
> > > > Signed-off-by: Matt Hsiao <matt.hsiao@xxxxxxx>
> > > > ---
> > > >
> > > > Hello contributors in the CC list,
> > > >
> > > > Thanks for your contributions to the hpilo driver. Please kindly
> > > > review the license change and hopefully you would agree and approve it.
> > Thanks!
> > > >
> > > > Patch v2:
> > > > ---------
> > > > - Change MODULE_LICENSE to Dual MIT/GPL too
> > >
> > > As I asked for on the v1 version (delayed email on my side), I need a
> > > lawyer from HPE to sign off on this change as well.
> > >
> > > thanks,
> > >
> > > greg k-h
> > 
> > Add HPE attorney Aahit Gaba to sign off.
> 
> Signed-off-by: Aahit Gaba <aahit.gaba@xxxxxxx>
> 
> The reasons we want to dual license Linux hpilo driver are:
> - There are required bug fixes that are not copyrighted by HPE in the current Linux hpilo driver.

And have you identified them and gotten a sign-off from those copyright
holders?  I don't see that here documented at all, so I imagine you
documented it somewhere else?  If so, where?

> - We want to maintain one hpilo driver between Linux and OpenBSD, and dual-licensing of hpilo driver's existing codebase and all the future bug fixes are the requirements for it. Therefore, we requested all other copyright owners of Linux hpilo driver to accept dual-licensing (MIT/GPL-2.0) for their respective contributions.

You can request, you can not require, right?

How are you going to deal with the fact that the driver really can not
be shared between these two operating systems without a lot of rewriting
and changing of the code?

Also, this code uses GPL-only symbols out of the Linux kernel, how are
you going to handle them in openbsd?  Do you have a port of the code to
openbsd somewhere for review that shows how this all is translated?

And this is really a tiny driver, why not just rewrite it from scratch
for openbsd anyway?  Odds are that's going to be required to fit into
the openbsd driver and coding style, right?

thanks,

greg k-h