From: Jakub Kicinski <kuba@kernel.org>
To: Rob Herring <robh@kernel.org>
Cc: Udit Kumar <u-kumar1@ti.com>,
vigneshr@ti.com, nm@ti.com, tglx@linutronix.de,
tpiepho@impinj.com, w.egorov@phytec.de, andrew@lunn.ch,
davem@davemloft.net, edumazet@google.com, pabeni@redhat.com,
krzk+dt@kernel.org, conor+dt@kernel.org, netdev@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Kip Broadhurst <kbroadhurst@ti.com>
Subject: Re: [PATCH v2] dt-bindings: net: dp8386x: Add MIT license along with GPL-2.0
Date: Wed, 5 Jun 2024 12:23:30 -0700 [thread overview]
Message-ID: <20240605122330.169ea734@kernel.org> (raw)
In-Reply-To: <20240605155659.GA3213669-robh@kernel.org>
On Wed, 5 Jun 2024 09:56:59 -0600 Rob Herring wrote:
> > Cc: Kip Broadhurst <kbroadhurst@ti.com>
Kip, ack?
Failing that (+1 to I'm not a lawyer, but) Udit, you both have @ti.com
addresses, can you confirm the intellectual rights are with TI?
In which case we won't have to wait for Kip.. Obviously easiest if they
just ack.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Jakub Kicinski <kuba@kernel.org>
To: Rob Herring <robh@kernel.org>
Cc: Udit Kumar <u-kumar1@ti.com>,
vigneshr@ti.com, nm@ti.com, tglx@linutronix.de,
tpiepho@impinj.com, w.egorov@phytec.de, andrew@lunn.ch,
davem@davemloft.net, edumazet@google.com, pabeni@redhat.com,
krzk+dt@kernel.org, conor+dt@kernel.org, netdev@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Kip Broadhurst <kbroadhurst@ti.com>
Subject: Re: [PATCH v2] dt-bindings: net: dp8386x: Add MIT license along with GPL-2.0
Date: Wed, 5 Jun 2024 12:23:30 -0700 [thread overview]
Message-ID: <20240605122330.169ea734@kernel.org> (raw)
In-Reply-To: <20240605155659.GA3213669-robh@kernel.org>
On Wed, 5 Jun 2024 09:56:59 -0600 Rob Herring wrote:
> > Cc: Kip Broadhurst <kbroadhurst@ti.com>
Kip, ack?
Failing that (+1 to I'm not a lawyer, but) Udit, you both have @ti.com
addresses, can you confirm the intellectual rights are with TI?
In which case we won't have to wait for Kip.. Obviously easiest if they
just ack.
next prev parent reply other threads:[~2024-06-05 19:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-31 16:57 [PATCH v2] dt-bindings: net: dp8386x: Add MIT license along with GPL-2.0 Udit Kumar
2024-05-31 16:57 ` Udit Kumar
2024-05-31 17:48 ` Wadim Egorov
2024-05-31 17:48 ` Wadim Egorov
2024-06-05 15:56 ` Rob Herring
2024-06-05 15:56 ` Rob Herring
2024-06-05 19:23 ` Jakub Kicinski [this message]
2024-06-05 19:23 ` Jakub Kicinski
2024-06-06 4:44 ` Kumar, Udit
2024-06-06 4:44 ` Kumar, Udit
2024-06-07 11:20 ` patchwork-bot+netdevbpf
2024-06-07 11:20 ` patchwork-bot+netdevbpf
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=20240605122330.169ea734@kernel.org \
--to=kuba@kernel.org \
--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=linux-arm-kernel@lists.infradead.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=tglx@linutronix.de \
--cc=tpiepho@impinj.com \
--cc=u-kumar1@ti.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.