[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <175807081736.540394.10309376848327644681.b4-ty@codeconstruct.com.au>
Date: Wed, 17 Sep 2025 10:30:17 +0930
From: Andrew Jeffery <andrew@...econstruct.com.au>
To: patrick@...cx.xyz, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>, Joel Stanley <joel@....id.au>,
Kees Cook <kees@...nel.org>, Tony Luck <tony.luck@...el.com>,
"Guilherme G. Piccoli" <gpiccoli@...lia.com>, Zane Li <Zane_Li@...ynn.com>
Cc: Zane Li <zane_li@...ynn.com>, devicetree@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-aspeed@...ts.ozlabs.org,
linux-kernel@...r.kernel.org, linux-hardening@...r.kernel.org
Subject: Re: [PATCH v1 1/1] ARM: dts: aspeed: yosemite4: allocate ramoops
for kernel panic
On Tue, 16 Sep 2025 11:40:35 +0800, Zane Li wrote:
> Reserve a ramoops memory region in the Yosemite4 device tree so that
> kernel panic logs can be preserved across reboots. This helps with
> post-mortem debugging and crash analysis.
>
>
Thanks, I've applied this to the BMC tree.
--
Andrew Jeffery <andrew@...econstruct.com.au>
Powered by blists - more mailing lists