Linux Tegra architecture development
 help / color / mirror / Atom feed
From: Peter De Schrijver <pdeschrijver@nvidia.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: <thierry.reding@gmail.com>, <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 v3 5/6] dt-bindings: memory-region property for tegra186-bpmp
Date: Thu, 11 May 2023 13:31:49 +0300	[thread overview]
Message-ID: <ZFzEFRBKMcUgrILn@44189d9-lcedt> (raw)
In-Reply-To: <5d01e717-39f1-798b-dda8-022b8430dc7d@linaro.org>

On Thu, May 11, 2023 at 11:03:24AM +0200, Krzysztof Kozlowski wrote:
> On 11/05/2023 10:04, Peter De Schrijver wrote:
> > On Wed, May 10, 2023 at 05:01:55PM +0200, Krzysztof Kozlowski wrote:
> >> On 10/05/2023 16:22, 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>
> >>> ---
> >>
> >> Also no changelog. Since I do not see improvements after Thierry
> >> comments I assume you send the same.
> >>
> > 
> > The changelog is in the cover letter. I will send it to you next
> > iteration.
> 
> I got only few patches, rest is missing including changelog. Thus it is
> the same as it did not exist.
> 

Do you want all of them? Some people seem to object to that so I didn't
send them to all people.

Peter.

  reply	other threads:[~2023-05-11 10:32 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-10 14:22 [PATCH v3 0/6] firmware: tegra: Add MRQ support for Tegra264 Peter De Schrijver
2023-05-10 14:22 ` [PATCH v3 1/6] dt-bindings: mailbox: tegra: Document Tegra264 HSP Peter De Schrijver
2023-05-10 15:00   ` Krzysztof Kozlowski
2023-05-10 14:22 ` [PATCH v3 2/6] mailbox: tegra: add support for Tegra264 Peter De Schrijver
2023-05-10 14:22 ` [PATCH v3 3/6] soc: tegra: fuse: " Peter De Schrijver
2023-05-10 14:22 ` [PATCH v3 4/6] dt-bindings: Add bindings to support DRAM MRQ GSCs Peter De Schrijver
2023-05-10 15:01   ` Krzysztof Kozlowski
2023-05-10 14:22 ` [PATCH v3 5/6] dt-bindings: memory-region property for tegra186-bpmp Peter De Schrijver
2023-05-10 15:01   ` Krzysztof Kozlowski
2023-05-11  8:04     ` Peter De Schrijver
2023-05-11  9:03       ` Krzysztof Kozlowski
2023-05-11 10:31         ` Peter De Schrijver [this message]
2023-05-11 16:58           ` Krzysztof Kozlowski
2023-05-10 14:22 ` [PATCH v3 6/6] firmware: tegra: bpmp: Add support for DRAM MRQ GSCs Peter De Schrijver
2023-05-10 14:43 ` [PATCH v3 0/6] firmware: tegra: Add MRQ support for Tegra264 Thierry Reding

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=ZFzEFRBKMcUgrILn@44189d9-lcedt \
    --to=pdeschrijver@nvidia.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jonathanh@nvidia.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=stefank@nvidia.com \
    --cc=thierry.reding@gmail.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