From: Thierry Reding <thierry.reding@gmail.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: arm@kernel.org, soc@kernel.org, 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: Wed, 23 Nov 2022 12:36:21 +0100 [thread overview]
Message-ID: <Y34FtfuIgHV9F6wS@orome> (raw)
In-Reply-To: <4994fbb1-72d2-4d21-bfb9-c1eefd9815fe@app.fastmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 956 bytes --]
On Tue, Nov 22, 2022 at 11:09:43PM +0100, Arnd Bergmann wrote:
> 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.
This is more of a safety net we've used in the past to make sure we can
run even if the bootloader doesn't add these. I also know that Jon was
running into some issues if these were not specified.
Jon, can we add a TODO item that we go over some of these and verify
which ones we need and which ones we don't. If we need them it might be
worth looking into why that is and if there isn't a better way to fix
this.
Thierry
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2022-11-23 11:37 UTC|newest]
Thread overview: 14+ 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
2022-11-23 11:36 ` Thierry Reding [this message]
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=Y34FtfuIgHV9F6wS@orome \
--to=thierry.reding@gmail.com \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=jonathanh@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-tegra@vger.kernel.org \
--cc=soc@kernel.org \
/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