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

[Greg KH]

On Tue, Feb 14, 2023 at 04:30:17PM +0800, Matt Hsiao wrote:
> On Fri, Feb 10, 2023 at 12:29:53PM +0100, Greg KH wrote:
> > 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 are under the assumption that hpilo contributors would reply to this
> thread with their 'Acked-by' or 'Signed-off-by'. Is that the proper
> approach?

Please work with your legal team to do this properly, they know what to
do here.  If not, then just don't worry about it (i.e. if it costs too
much to do this, just spend the money to write a second driver.)

> We shouldn't have used the term 'one driver'. More accurate description
> is we want the core driver features and any changes or bug fixes apply
> to that dual licensed. We understand that the parts of the driver that
> are calls to Linux specific functions would be different in OpenBSD.
> There are also some Linux infrastructure things that would be different
> in OpenBSD. The key for us is that the core driver features and any
> future changes be kept in sync between Linux and OpenBSD.

Again, you have full control over this as you are making those changes
yourself.  I really don't see why you need to do this.

Write the OpenBSD driver yourself and see if you could actually share
anything.  Odds are, the shared parts you already have copyright over
today, so there's no issues involved.

good luck!

greg k-h