From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Sam Protsenko <semen.protsenko@linaro.org>
Cc: Conor Dooley <conor+dt@kernel.org>,
Alim Akhtar <alim.akhtar@samsung.com>,
Kees Cook <keescook@chromium.org>,
Tony Luck <tony.luck@intel.com>,
"Guilherme G. Piccoli" <gpiccoli@igalia.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-hardening@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: exynos: Add reserved memory for pstore on E850-96
Date: Thu, 12 Oct 2023 22:03:25 +0200 [thread overview]
Message-ID: <72cf8478-9683-4ea8-830f-fcb46b583f2b@linaro.org> (raw)
In-Reply-To: <169714096778.12426.2726125345142435040.b4-ty@linaro.org>
On 12/10/2023 22:02, Krzysztof Kozlowski wrote:
>
> On Sat, 07 Oct 2023 22:36:33 -0500, Sam Protsenko wrote:
>> Reserve a 2 MiB memory region to record kmsg dumps, console, ftrace and
>> userspace messages. The implemented memory split allows capturing and
>> reading corresponding ring buffers:
>> * dmesg: 6 dumps, 128 KiB each
>> * console: 128 KiB
>> * ftrace: 128 KiB for each of 8 CPUs (1 MiB total)
>> * userspace messages: 128 KiB
>>
>> [...]
>
> Applied, thanks!
>
> [1/1] arm64: dts: exynos: Add reserved memory for pstore on E850-96
> https://git.kernel.org/krzk/linux/c/23e4a49943624dd83199989c852565a3ff760fa7
Thanks, applied.
It is however very late in the cycle, so there is a chance this will
miss the merge window. If this happens, I will keep it for the next
cycle (no need for resending).
Best regards,
Krzysztof
prev parent reply other threads:[~2023-10-12 20:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-08 3:36 [PATCH] arm64: dts: exynos: Add reserved memory for pstore on E850-96 Sam Protsenko
2023-10-12 20:02 ` Krzysztof Kozlowski
2023-10-12 20:03 ` Krzysztof Kozlowski [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=72cf8478-9683-4ea8-830f-fcb46b583f2b@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=alim.akhtar@samsung.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gpiccoli@igalia.com \
--cc=keescook@chromium.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=semen.protsenko@linaro.org \
--cc=tony.luck@intel.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;
as well as URLs for NNTP newsgroup(s).