From: Konrad Dybcio <konrad.dybcio@linaro.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Kees Cook <keescook@chromium.org>,
Tony Luck <tony.luck@intel.com>,
"Guilherme G. Piccoli" <gpiccoli@igalia.com>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org
Subject: Re: [PATCH 4/7] arm64: dts: qcom: sm6125-sprout: correct ramoops pmsg-size
Date: Mon, 19 Jun 2023 11:57:07 +0200 [thread overview]
Message-ID: <ad29a143-c6bf-7c13-a085-a33b63351d5a@linaro.org> (raw)
In-Reply-To: <20230618114442.140185-4-krzysztof.kozlowski@linaro.org>
On 18.06.2023 13:44, Krzysztof Kozlowski wrote:
> There is no 'msg-size' property in ramoops, so assume intention was for
> 'pmsg-size':
>
> sm6125-xiaomi-laurel-sprout.dtb: ramoops@ffc00000: Unevaluated properties are not allowed ('msg-size' was unexpected)
>
> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> ---
Reviewed-by: Konrad Dybcio <konrad.dybcio@linaro.org>
Konrad
> arch/arm64/boot/dts/qcom/sm6125-xiaomi-laurel-sprout.dts | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arm64/boot/dts/qcom/sm6125-xiaomi-laurel-sprout.dts b/arch/arm64/boot/dts/qcom/sm6125-xiaomi-laurel-sprout.dts
> index a7f4aeae9c1a..7c58d1299a60 100644
> --- a/arch/arm64/boot/dts/qcom/sm6125-xiaomi-laurel-sprout.dts
> +++ b/arch/arm64/boot/dts/qcom/sm6125-xiaomi-laurel-sprout.dts
> @@ -52,7 +52,7 @@ pstore_mem: ramoops@ffc00000 {
> reg = <0x0 0xffc40000 0x0 0xc0000>;
> record-size = <0x1000>;
> console-size = <0x40000>;
> - msg-size = <0x20000 0x20000>;
> + pmsg-size = <0x20000>;
> };
>
> cmdline_mem: memory@ffd00000 {
next prev parent reply other threads:[~2023-06-19 9:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-18 11:44 [PATCH 1/7] arm64: dts: qcom: sm8350-hdk: correct FSA4480 port Krzysztof Kozlowski
2023-06-18 11:44 ` [PATCH 2/7] arm64: dts: qcom: sm8450-hdk: " Krzysztof Kozlowski
2023-06-19 8:11 ` Neil Armstrong
2023-06-18 11:44 ` [PATCH 3/7] arm64: dts: qcom: sm6125-pdx201: correct ramoops pmsg-size Krzysztof Kozlowski
2023-06-19 9:56 ` Konrad Dybcio
2023-06-18 11:44 ` [PATCH 4/7] arm64: dts: qcom: sm6125-sprout: " Krzysztof Kozlowski
2023-06-19 9:57 ` Konrad Dybcio [this message]
2023-06-18 11:44 ` [PATCH 5/7] arm64: dts: qcom: sm6350: " Krzysztof Kozlowski
2023-06-19 9:57 ` Konrad Dybcio
2023-06-18 11:44 ` [PATCH 6/7] arm64: dts: qcom: sm8150-kumano: " Krzysztof Kozlowski
2023-06-19 9:57 ` Konrad Dybcio
2023-06-18 11:44 ` [PATCH 7/7] arm64: dts: qcom: sm8250-edo: " Krzysztof Kozlowski
2023-06-19 9:57 ` Konrad Dybcio
2023-06-19 8:11 ` [PATCH 1/7] arm64: dts: qcom: sm8350-hdk: correct FSA4480 port Neil Armstrong
2023-07-10 5:07 ` (subset) " Bjorn Andersson
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=ad29a143-c6bf-7c13-a085-a33b63351d5a@linaro.org \
--to=konrad.dybcio@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--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=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.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).