From: Greg KH <gregkh@linuxfoundation.org>
To: matt.hsiao@hpe.com
Cc: linux-kernel@vger.kernel.org, arnd@arndb.de,
christophe.jaillet@wanadoo.fr, gustavoars@kernel.org,
nishadkamdar@gmail.com, torvalds@linux-foundation.org,
dhaval.experiance@gmail.com, viro@zeniv.linux.org.uk,
arvind.yadav.cs@gmail.com, standby24x7@gmail.com,
wfp5p@virginia.edu, jslaby@suse.cz, prarit@redhat.com,
tj@kernel.org, adobriyan@gmail.com
Subject: Re: [PATCH v2] misc: hpilo: relicense HPE iLO driver as Dual MIT/GPL
Date: Wed, 16 Nov 2022 12:36:40 +0100 [thread overview]
Message-ID: <Y3TLSON/7XRG5BiN@kroah.com> (raw)
In-Reply-To: <20221116103457.27486-1-matt.hsiao@hpe.com>
On Wed, Nov 16, 2022 at 06:34:57PM +0800, matt.hsiao@hpe.com wrote:
> From: Matt Hsiao <matt.hsiao@hpe.com>
>
> 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@hpe.com>
> ---
>
> 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
next prev parent reply other threads:[~2022-11-16 11:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-16 10:34 [PATCH v2] misc: hpilo: relicense HPE iLO driver as Dual MIT/GPL matt.hsiao
2022-11-16 11:06 ` Jiri Slaby
2022-11-16 11:36 ` Greg KH [this message]
2023-02-09 3:38 ` Matt Hsiao
2023-02-09 3:59 ` Gaba, Aahit
2023-02-10 11:29 ` Greg KH
2023-02-14 8:30 ` Matt Hsiao
2023-02-14 8:52 ` Greg KH
2023-02-10 11:27 ` Greg KH
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=Y3TLSON/7XRG5BiN@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=adobriyan@gmail.com \
--cc=arnd@arndb.de \
--cc=arvind.yadav.cs@gmail.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=dhaval.experiance@gmail.com \
--cc=gustavoars@kernel.org \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.hsiao@hpe.com \
--cc=nishadkamdar@gmail.com \
--cc=prarit@redhat.com \
--cc=standby24x7@gmail.com \
--cc=tj@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
--cc=wfp5p@virginia.edu \
/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