Linux Tegra architecture development
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
To: Sameer Pujar <spujar@nvidia.com>, thierry.reding@gmail.com
Cc: jonathanh@nvidia.com, linux-kernel@vger.kernel.org,
	linux-tegra@vger.kernel.org
Subject: Re: [PATCH] memory: tegra: Add APE memory clients for Tegra234
Date: Fri, 18 Feb 2022 14:04:46 +0100	[thread overview]
Message-ID: <028f766d-e5ba-fc12-665c-8f65d6bdf817@canonical.com> (raw)
In-Reply-To: <1645186589-25118-1-git-send-email-spujar@nvidia.com>

On 18/02/2022 13:16, Sameer Pujar wrote:
> Add the memory clients on Tegra234 which are needed for APE
> DMA to properly use the SMMU.
> 
> Signed-off-by: Sameer Pujar <spujar@nvidia.com>
> ---
>  Please note that this patch depends on the DT binding patches of series
>  https://patchwork.kernel.org/project/alsa-devel/list/?series=609494&state=*.
>  So please consider this patch once Thierry picks up DT binding patches and
>  provides ACK on this.

I was not Cced on that patchset. Could you use
scripts/get_maintainers.pl for obtaining list of people and lists to Cc?

If Thierry picks up dt-bindings patch and I take this one, does it
compile? No, I don't think so. The order is screwed. This should be sent
together to make such dependencies obvious.

Anyway, I cannot take it so:
Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>


>  drivers/memory/tegra/tegra234.c | 22 +++++++++++++++++++++-
>  1 file changed, 21 insertions(+), 1 deletion(-)
> 


Best regards,
Krzysztof

  reply	other threads:[~2022-02-18 13:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-18 12:16 [PATCH] memory: tegra: Add APE memory clients for Tegra234 Sameer Pujar
2022-02-18 13:04 ` Krzysztof Kozlowski [this message]
2022-02-18 13:25   ` Thierry Reding
2022-02-21 15:41 ` kernel test robot

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=028f766d-e5ba-fc12-665c-8f65d6bdf817@canonical.com \
    --to=krzysztof.kozlowski@canonical.com \
    --cc=jonathanh@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=spujar@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