Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
From:   Vignesh Raghavendra <vigneshr@ti.com>
To:     Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
        Rob Herring <robh+dt@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>,
        Tero Kristo <kristo@kernel.org>
Subject: Re: [PATCH V2 0/5] arm64: dts: ti: Drop bootargs
Date:   Tue, 6 Jun 2023 22:48:22 +0530
Message-ID: <168607161907.2072651.9268020209509725261.b4-ty@ti.com>
In-Reply-To: <20230419141222.383567-1-nm@ti.com>
References: <20230419141222.383567-1-nm@ti.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

Hi Nishanth Menon,

On Wed, 19 Apr 2023 09:12:17 -0500, Nishanth Menon wrote:
> The bootargs atm contains (generally) two information: console and
> earlycon - console is already covered by stdout-path and earlycon is
> really meant to be used when debug is needed and not something of a
> default to spin out to all users.
> 
> This has come up multiple times, so cleaning it all up.
> See [1] for context. AM64 is covered in [2]. There are quite a few other
> instances of the same in mailing list[3].
> 
> [...]

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

[1/5] arm64: dts: ti: k3-am62x-sk-common: Drop bootargs
      commit: d525ef9c7f077bfa8202b4b47ca9242ab936a1dc
[2/5] arm64: dts: ti: k3-am65*: Drop bootargs
      commit: da4159a776593f802ee211ad4823f3aed31e5375
[3/5] arm64: dts: ti: k3-j721e-*: Drop bootargs
      commit: af2cda7df7769d3353170b6a72d73bc4ea703480
[4/5] arm64: dts: ti: k3-j7200-common-proc-board: Drop bootargs
      commit: f920c49f1e46a99c410e2aaf486ffb7ce3d12270
[5/5] arm64: dts: ti: k3-j721s2-common-proc-board: Drop bootargs
      commit: cf82a026f54f54c241903add9b9bdbeb2a449db0

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