lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <19f291d7-cb64-49b3-88e7-8541029cdf0d@ideasonboard.com>
Date: Thu, 12 Sep 2024 21:21:19 +0300
From: Tomi Valkeinen <tomi.valkeinen@...asonboard.com>
To: Maxime Ripard <mripard@...nel.org>, Devarsh Thakkar <devarsht@...com>
Cc: ahalaney@...hat.com, airlied@...il.com, cai.huoqing@...ux.dev,
 caihuoqing@...du.com, colin.i.king@...il.com, dakr@...hat.com,
 daniel@...ll.ch, dmitry.baryshkov@...aro.org,
 dri-devel@...ts.freedesktop.org, geert+renesas@...der.be,
 grandmaster@...klimov.de, j-choudhary@...com, javierm@...hat.com,
 jyri.sarha@....fi, laurent.pinchart@...asonboard.com,
 linux-kernel@...r.kernel.org, maarten.lankhorst@...ux.intel.com, nm@...com,
 praneeth@...com, r-ravikumar@...com, robh@...nel.org, sam@...nborg.org,
 simona.vetter@...ll.ch, tzimmermann@...e.de, u.kleine-koenig@...gutronix.de,
 vigneshr@...com, ville.syrjala@...ux.intel.com, wangxiaojun11@...wei.com,
 yuanjilin@...rlc.com, yuehaibing@...wei.com
Subject: Re: [PATCH] drm/tidss: Add MIT license along with GPL-2.0

On 12/09/2024 21:08, Maxime Ripard wrote:
> On Thu, Sep 12, 2024 at 06:04:11PM GMT, Maxime Ripard wrote:
>> On Thu, 12 Sep 2024 22:41:42 +0530, Devarsh Thakkar wrote:
>>> Modify license to include dual licensing as GPL-2.0-only OR MIT license for
>>> tidss display driver. This allows other operating system ecosystems such as
>>> Zephyr and also the commercial firmwares to refer and derive code from this
>>> display driver in a more permissive manner.
>>>
>>>
>>> [ ... ]
>>
>> Acked-by: Maxime Ripard <mripard@...nel.org>
> 
> Also, we need the ack of all contributors to that driver, so my ack
> isn't enough to merge that patch.

IANAL, maybe a silly question: if someone from company XYZ has sent a 
patch for tidss, don't we then need an ack from someone in XYZ who's 
high enough in XYZ to allow changing the license for their code?

  Tomi


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ