From: AngeloGioacchino Del Regno <[email protected]>
To: "Nícolas F. R. A. Prado" <[email protected]>,
"Matthias Brugger" <[email protected]>
Cc: [email protected],
Krzysztof Kozlowski <[email protected]>,
Rob Herring <[email protected]>,
[email protected], [email protected],
[email protected], [email protected]
Subject: Re: [PATCH] arm64: dts: mt8192: Follow binding order for SCP registers
Date: Wed, 4 May 2022 10:10:56 +0200 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
Il 03/05/22 23:25, Nícolas F. R. A. Prado ha scritto:
> The dt-binding for SCP documents the reg-names order as sram, cfg,
> l1tcm. Update the SCP node on the mt8192 devicetree to follow that
> order, which gets rid of a dtbs_check warning. This doesn't change any
> behavior since the SCP driver accesses the memory regions through the
> names anyway.
>
> Signed-off-by: Nícolas F. R. A. Prado <[email protected]>
Nic, you need a Fixes: tag on this commit, please add it and send a v2!
Cheers!
prev parent reply other threads:[~2022-05-04 8:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-03 21:25 [PATCH] arm64: dts: mt8192: Follow binding order for SCP registers Nícolas F. R. A. Prado
2022-05-04 8:10 ` AngeloGioacchino Del Regno [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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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