On 11:25-20240522, Conor Dooley wrote:
On Wed, May 22, 2024 at 10:04:39AM +0200, Paolo Abeni wrote:Just to close the loop here: Udit pointed me to this thread and having
On Mon, 2024-05-20 at 15:18 -0500, Rob Herring wrote:I don't think whether or not I agree matters, Rob said it's fine so it's
On Mon, May 20, 2024 at 06:17:52PM +0100, Conor Dooley wrote:Conor would you agree with Rob? - my take is that he is ok with this
On Sat, May 18, 2024 at 02:18:55PM +0530, Kumar, Udit wrote:Aligning with the DTS files is enough reason for me as that's where
Hi ConorUnless there's a specific reason to use MIT (like your legal won't even
On 5/17/2024 8:11 PM, Conor Dooley wrote:
On Fri, May 17, 2024 at 03:39:20PM +0100, Conor Dooley wrote:want to be inline with License of top level DTS, which is including this
On Fri, May 17, 2024 at 04:12:26PM +0530, Udit Kumar wrote:I cut myself off, I meant to say:
Modify license to include dual licensing as GPL-2.0-only OR MITWhat's wrong with BSD-2-Clause, why not use that?
license for TI specific phy header files. This allows for Linux
kernel files to be used in other Operating System ecosystems
such as Zephyr or FreeBSD.
What's wrong with BSD-2-Clause, the standard dual license for
bindings, why not use that?
header file
allow you to use BSD-2-Clause) then please just use the normal license
for bindings here.
these files are used. If you need to pick a permissive license for both,
then yes, use BSD-2-Clause. Better yet, ask your lawyer.
patch.
fine.
gone through this already[1] with internal TI teams, the feedback we
have gotten from our licensing team (including legal) is to go with
GPL2 or MIT. BSD (2 and 3 clauses) were considered, but due to varied
reasons, dropped.
That said, Udit, since you are touching this, please update in the next
revision:
Copyright: (C) 2015-2024 Texas Instruments, Inc.
to
Copyright (C) 2015-2024 Texas Instruments Incorporated - https://www.ti.com/
[1] https://serenity.dal.design.ti.com/lore/linux-patch-review/20240109231804.3879513-1-nm@xxxxxx/