From: "Arnd Bergmann" <arnd@arndb.de>
To: "Thierry Reding" <thierry.reding@gmail.com>,
arm@kernel.org, soc@kernel.org
Cc: "Jon Hunter" <jonathanh@nvidia.com>,
linux-tegra@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL v2 7/7] arm64: tegra: Device tree changes for v6.2-rc1
Date: Tue, 22 Nov 2022 23:09:43 +0100 [thread overview]
Message-ID: <4994fbb1-72d2-4d21-bfb9-c1eefd9815fe@app.fastmail.com> (raw)
In-Reply-To: <20221121171239.2041835-7-thierry.reding@gmail.com>
On Mon, Nov 21, 2022, at 18:12, Thierry Reding wrote:
>
> Jon Hunter (6):
> arm64: tegra: Update console for Jetson Xavier and Orin
While this change is clearly correct, I think it would be even
better to completely drop the chosen/bootargs property completely
here. The bootargs are meant to come from the bootloader anyway,
and the console= argument is already implicitly set through the
chosen/stdout-path property.
Arnd
next prev parent reply other threads:[~2022-11-22 22:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-21 17:12 [GIT PULL v2 1/7] soc/tegra: Changes for v6.2-rc1 Thierry Reding
2022-11-21 17:12 ` [GIT PULL v2 2/7] firmware: tegra: " Thierry Reding
2022-11-22 21:25 ` Arnd Bergmann
2022-11-23 11:33 ` Thierry Reding
2022-11-23 13:23 ` Arnd Bergmann
2022-11-25 10:12 ` Thierry Reding
2022-11-21 17:12 ` [GIT PULL v2 3/7] clk: " Thierry Reding
2022-11-21 17:12 ` [GIT PULL v2 4/7] dt-bindings: " Thierry Reding
2022-11-29 17:16 ` Rob Herring
2022-11-21 17:12 ` [GIT PULL v2 5/7] memory: tegra: " Thierry Reding
2022-11-21 17:12 ` [GIT PULL v2 6/7] ARM: tegra: Device tree changes " Thierry Reding
2022-11-21 17:12 ` [GIT PULL v2 7/7] arm64: " Thierry Reding
2022-11-22 22:09 ` Arnd Bergmann [this message]
2022-11-23 11:36 ` Thierry Reding
2022-11-22 22:20 ` [GIT PULL v2 1/7] soc/tegra: Changes " patchwork-bot+linux-soc
2022-11-23 12:00 ` patchwork-bot+linux-soc
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=4994fbb1-72d2-4d21-bfb9-c1eefd9815fe@app.fastmail.com \
--to=arnd@arndb.de \
--cc=arm@kernel.org \
--cc=jonathanh@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-tegra@vger.kernel.org \
--cc=soc@kernel.org \
--cc=thierry.reding@gmail.com \
/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