From: "Kumar, Udit" <u-kumar1@ti.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: <vigneshr@ti.com>, <nm@ti.com>, <davem@davemloft.net>,
<edumazet@google.com>, <kuba@kernel.org>, <pabeni@redhat.com>,
<robh@kernel.org>, <krzk+dt@kernel.org>, <conor+dt@kernel.org>,
<netdev@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
Kip Broadhurst <kbroadhurst@ti.com>, <w.egorov@phytec.de>
Subject: Re: [PATCH] dt-bindings: net: dp8386x: Add MIT license along with GPL-2.0
Date: Fri, 17 May 2024 19:47:06 +0530 [thread overview]
Message-ID: <7439c9e1-59cd-4d37-aab8-bc71b6a98a09@ti.com> (raw)
In-Reply-To: <41e30085-937a-410a-ac6a-189307a59319@lunn.ch>
Thanks Andrew
On 5/17/2024 7:26 PM, Andrew Lunn wrote:
> On Fri, May 17, 2024 at 04:12:26PM +0530, Udit Kumar wrote:
>> Modify license to include dual licensing as GPL-2.0-only OR MIT
>> 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.
>>
>> While at this, update the TI copyright year to sync with current year
>> to indicate license change.
>>
>> Cc: Kip Broadhurst <kbroadhurst@ti.com>
>> Signed-off-by: Udit Kumar <u-kumar1@ti.com>
>> ---
>> include/dt-bindings/net/ti-dp83867.h | 4 ++--
>> include/dt-bindings/net/ti-dp83869.h | 4 ++--
>> 2 files changed, 4 insertions(+), 4 deletions(-)
>>
>> diff --git a/include/dt-bindings/net/ti-dp83867.h b/include/dt-bindings/net/ti-dp83867.h
>> index 6fc4b445d3a1..2b7bc9c692f2 100644
>> --- a/include/dt-bindings/net/ti-dp83867.h
>> +++ b/include/dt-bindings/net/ti-dp83867.h
>> @@ -1,10 +1,10 @@
>> -/* SPDX-License-Identifier: GPL-2.0-only */
>> +/* SPDX-License-Identifier: GPL-2.0-only OR MIT */
>> /*
>> * Device Tree constants for the Texas Instruments DP83867 PHY
>> *
>> * Author: Dan Murphy <dmurphy@ti.com>
>> *
>> - * Copyright: (C) 2015 Texas Instruments, Inc.
>> + * Copyright: (C) 2015-2024 Texas Instruments, Inc.
>> */
> IANAL
>
> but about 1/4 of this file was written by Wadim Egorov
> <w.egorov@phytec.de>. It would be good to Cc: him and make sure he
> does not object.
Wadim is copied.
Also will take care of copying in next version if any.
> The other file is fine, it was all Dan Murphy's work.
>
> Andrew
next prev parent reply other threads:[~2024-05-17 15:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-17 10:42 [PATCH] dt-bindings: net: dp8386x: Add MIT license along with GPL-2.0 Udit Kumar
2024-05-17 13:56 ` Andrew Lunn
2024-05-17 14:17 ` Kumar, Udit [this message]
2024-05-17 14:39 ` Conor Dooley
2024-05-17 14:41 ` Conor Dooley
2024-05-18 8:48 ` Kumar, Udit
2024-05-20 17:17 ` Conor Dooley
2024-05-20 20:18 ` Rob Herring
2024-05-22 8:04 ` Paolo Abeni
2024-05-22 10:25 ` Conor Dooley
2024-05-22 13:40 ` Nishanth Menon
2024-05-22 15:37 ` Conor Dooley
2024-05-22 17:39 ` Kumar, Udit
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=7439c9e1-59cd-4d37-aab8-bc71b6a98a09@ti.com \
--to=u-kumar1@ti.com \
--cc=andrew@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=kbroadhurst@ti.com \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nm@ti.com \
--cc=pabeni@redhat.com \
--cc=robh@kernel.org \
--cc=vigneshr@ti.com \
--cc=w.egorov@phytec.de \
/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;
as well as URLs for NNTP newsgroup(s).