Received-SPF: pass (google.com: domain of linux-kernel+bounces-55153-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45e3:2400::1 as permitted sender) client-ip=2604:1380:45e3:2400::1;
From: Vignesh Raghavendra <vigneshr@ti.com>
To: Tero Kristo <kristo@kernel.org>, Nishanth Menon <nm@ti.com>
CC: Vignesh Raghavendra <vigneshr@ti.com>, <linux-kernel@vger.kernel.org>,
        <devicetree@vger.kernel.org>, <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH V2 00/16] arm64: dts: ti: Additional licensing and clarification
Date: Tue, 6 Feb 2024 20:24:40 +0530
Message-ID: <170723117278.3216299.12458152939034721597.b4-ty@ti.com>
In-Reply-To: <20240122145539.194512-1-nm@ti.com>
References: <20240122145539.194512-1-nm@ti.com>
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit

Hi Nishanth Menon,

On Mon, 22 Jan 2024 08:55:23 -0600, Nishanth Menon wrote:
> Thank you all for the detailed acks on various patches on V1,
> consolidated all of these with V2 and noted some missing acks below.
> Since it has been 12 days since I posted v1 and v6.8-rc1 is now
> tagged, looks like a good time to refresh the series.
> 
> As part of my 2023 LPC talk[1] about the difficulty in ensuring
> device tree is same across multiple s/w ecosystems, I mentioned about
> Licensing, and Rob had indicated that other SoC vendors have MIT
> license option that allows co-existance with Apache.
> 
> [...]

I have applied the following to branch ti-k3-dts-next on [1].
Thank you!

[01/16] arm64: dts: ti: Use https for urls
        commit: 01e886c4dfdacc2956d9857a3b5c985ea74e9ddd
[02/16] arm64: dts: ti: k3-am62a7: Add MIT license along with GPL-2.0
        commit: 89bd4c373649b81d4255d9c5a3e49d3fd10df708
[03/16] arm64: dts: ti: k3-am625: Add MIT license along with GPL-2.0
        commit: 7e614b5394f06c7ff5e9ef570bb1d40af08c6449
[04/16] arm64: dts: ti: k3-am62p: Add MIT license along with GPL-2.0
        commit: 20f8173afaac90dd9dca11be4aa602a47776077f
[05/16] arm64: dts: ti: k3-am64: Add MIT license along with GPL-2.0
        commit: 6248b20e3203c5f255efe6c330b5c871ca4e8033
[06/16] arm64: dts: ti: k3-am65: Add MIT license along with GPL-2.0
        commit: 2822c791af4d98ca469485dacde9ea4f13c905af
[07/16] arm64: dts: ti: k3-j7200: Add MIT license along with GPL-2.0
        commit: b87c44dd974e13aab1d0a9a01a5f94f1fe5fd1fb
[08/16] arm64: dts: ti: k3-j721e: Add MIT license along with GPL-2.0
        commit: 111f6dac6c08471888da49389f63174f3717bfbd
[09/16] arm64: dts: ti: k3-j721s2: Add MIT license along with GPL-2.0
        commit: 25aec8a64a2413f6b16e33ecbc0334bd7075ba49
[10/16] arm64: dts: ti: k3-j784s4: Add MIT license along with GPL-2.0
        commit: 33e089bd1e136f1e2c58e6b44455de55f4fe4bae
[11/16] arm64: dts: ti: k3-pinctrl: Add MIT license along with GPL-2.0
        commit: 67fdcf08cd76a7d81e64343b2f0730f554245840
[12/16] arm64: dts: ti: k3-serdes: Add MIT license along with GPL-2.0
        commit: 3feda6a0cf7d9a82d820032033ae7e600e9dca66
[13/16] arm64: dts: ti: beagle*: Add MIT license along with GPL-2.0
        commit: 380f1ffd281b6f33a6e03220921be2750c6fd8ce
[14/16] arm64: dts: ti: phycore*: Add MIT license along with GPL-2.0
        commit: 049010c9604f87568ae59ee5ea1b885ece19e6c6
[15/16] arm64: dts: ti: iot2050*: Clarify GPL-2.0 as GPL-2.0-only
        commit: c32953cf00a5ab9059483d825f866a528ad80460
[16/16] arm64: dts: ti: Makefile: Clarify GPL-2.0 as GPL-2.0-only
        commit: 1e6bbc5185bcd113c8d2f7aa0a02f588a6bdbe5d

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent up the chain during
the next merge window (or sooner if it is a relevant bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

[1] https://git.kernel.org/pub/scm/linux/kernel/git/ti/linux.git
--
Vignesh