The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: "Kumar, Udit" <u-kumar1@ti.com>
To: Conor Dooley <conor@kernel.org>
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: Sat, 18 May 2024 14:18:55 +0530	[thread overview]
Message-ID: <8e56ea52-9e58-4291-8f7f-4721dd74c72f@ti.com> (raw)
In-Reply-To: <20240517-fastball-stable-9332cae850ea@spud>

Hi Conor

On 5/17/2024 8:11 PM, Conor Dooley wrote:
> On Fri, May 17, 2024 at 03:39:20PM +0100, Conor Dooley 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.
>> What's wrong with BSD-2-Clause, why not use that?
> I cut myself off, I meant to say:
> What's wrong with BSD-2-Clause, the standard dual license for
> bindings, why not use that?

want to be inline with License of top level DTS, which is including this 
header file

eg

https://elixir.bootlin.com/linux/latest/source/arch/arm64/boot/dts/ti/k3-j722s-evm.dts#L1 



  reply	other threads:[~2024-05-18  8:49 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
2024-05-17 14:39 ` Conor Dooley
2024-05-17 14:41   ` Conor Dooley
2024-05-18  8:48     ` Kumar, Udit [this message]
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=8e56ea52-9e58-4291-8f7f-4721dd74c72f@ti.com \
    --to=u-kumar1@ti.com \
    --cc=conor+dt@kernel.org \
    --cc=conor@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