From: Thierry Reding <thierry.reding@gmail.com>
To: Peter De Schrijver <pdeschrijver@nvidia.com>
Cc: jonathanh@nvidia.com, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
devicetree@vger.kernel.org, linux-tegra@vger.kernel.org,
linux-kernel@vger.kernel.org, stefank@nvidia.com
Subject: Re: [PATCH v2 5/6] dt-bindings: memory-region property for tegra186-bpmp
Date: Wed, 10 May 2023 16:40:26 +0200 [thread overview]
Message-ID: <ZFus2s7rdIS4hf0S@orome> (raw)
In-Reply-To: <20230510113129.4167493-6-pdeschrijver@nvidia.com>
[-- Attachment #1: Type: text/plain, Size: 848 bytes --]
On Wed, May 10, 2023 at 02:31:34PM +0300, Peter De Schrijver wrote:
> Add memory-region property to the tegra186-bpmp binding to support
> DRAM MRQ GSCs.
>
> Co-developed-by: Stefan Kristiansson <stefank@nvidia.com>
> Signed-off-by: Stefan Kristiansson <stefank@nvidia.com>
> Signed-off-by: Peter De Schrijver <pdeschrijver@nvidia.com>
> ---
> .../firmware/nvidia,tegra186-bpmp.yaml | 37 +++++++++++++++++--
> 1 file changed, 34 insertions(+), 3 deletions(-)
We usually use a longer subject prefix, even though that makes the whole
subject usually become longer than the recommended 50 (or so)
characters.
Maybe you also want to add a verb to the subject to make it more
descriptive. As it is the subject doesn't indicate what's happening with
the memory-region property. It could equally well get removed.
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-05-10 14:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-10 11:31 [PATCH v2 0/6] firmware: tegra: Add MRQ support for Tegra264 Peter De Schrijver
2023-05-10 11:31 ` [PATCH v2 1/6] dt-bindings: mailbox: tegra: Document Tegra264 HSP Peter De Schrijver
2023-05-10 13:50 ` Thierry Reding
2023-05-10 11:31 ` [PATCH v2 2/6] mailbox: tegra: add support for Tegra264 Peter De Schrijver
2023-05-10 13:50 ` Thierry Reding
2023-05-10 11:31 ` [PATCH v2 3/6] soc: tegra: fuse: " Peter De Schrijver
2023-05-10 14:35 ` Thierry Reding
2023-05-10 11:31 ` [PATCH v2 4/6] dt-bindings: Add bindings to support DRAM MRQ GSCs Peter De Schrijver
2023-05-10 12:47 ` Krzysztof Kozlowski
2023-05-10 11:31 ` [PATCH v2 5/6] dt-bindings: memory-region property for tegra186-bpmp Peter De Schrijver
2023-05-10 14:40 ` Thierry Reding [this message]
2023-05-10 11:31 ` [PATCH v2 6/6] firmware: tegra: bpmp: Add support for DRAM MRQ GSCs Peter De Schrijver
2023-05-10 14:33 ` Thierry Reding
2023-05-11 8:04 ` Peter De Schrijver
2023-05-10 11:44 ` [PATCH v2 0/6] firmware: tegra: Add MRQ support for Tegra264 Peter De Schrijver
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=ZFus2s7rdIS4hf0S@orome \
--to=thierry.reding@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=pdeschrijver@nvidia.com \
--cc=robh+dt@kernel.org \
--cc=stefank@nvidia.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).