From: Mohan Kumar D <mkumard@nvidia.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: vkoul@kernel.org, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, dmaengine@vger.kernel.org,
devicetree@vger.kernel.org, linux-tegra@vger.kernel.org,
linux-kernel@vger.kernel.org, thierry.reding@gmail.com,
jonathanh@nvidia.com, spujar@nvidia.com
Subject: Re: [PATCH v2 1/2] dt-bindings: dma: Support channel page to nvidia,tegra210-adma
Date: Mon, 16 Dec 2024 17:11:49 +0530 [thread overview]
Message-ID: <c632fbb3-ef74-428a-a2e6-eb178f430824@nvidia.com> (raw)
In-Reply-To: <x3cp6ho3ovwwarj3767ryoufvcqh5fe5fabtsjvrsg6ek6gjqz@iezeaqtav77o>
On 16-12-2024 15:00, Krzysztof Kozlowski wrote:
> External email: Use caution opening links or attachments
>
>
> On Fri, Dec 13, 2024 at 04:09:38PM +0530, Mohan Kumar D wrote:
>> Multiple ADMA Channel page hardware support has been added from
>> TEGRA186 and onwards. Update the DT binding to use any of the
>> ADMA channel page address space region.
>>
>> Signed-off-by: Mohan Kumar D <mkumard@nvidia.com>
>> ---
> This is v2 but no changelog, no explanation whatsoever... I assume
> feedback was not implemented, so please go back to previous version and
> address the feedback and then send proper new version with changelog.
>
> See submitting patches.
It's my bad to not include the changelog info, though I have taken care
of the feedback on the ADMA DT bindings. I will include the changelog
info and resend the v2.
>
> Best regards,
> Krzysztof
>
next prev parent reply other threads:[~2024-12-16 11:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-13 10:39 [PATCH v2 0/2] Add Tegra ADMA channel page support Mohan Kumar D
2024-12-13 10:39 ` [PATCH v2 1/2] dt-bindings: dma: Support channel page to nvidia,tegra210-adma Mohan Kumar D
2024-12-16 9:30 ` Krzysztof Kozlowski
2024-12-16 11:41 ` Mohan Kumar D [this message]
2024-12-13 10:39 ` [PATCH v2 2/2] dmaengine: tegra210-adma: Support channel page Mohan Kumar D
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=c632fbb3-ef74-428a-a2e6-eb178f430824@nvidia.com \
--to=mkumard@nvidia.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=robh@kernel.org \
--cc=spujar@nvidia.com \
--cc=thierry.reding@gmail.com \
--cc=vkoul@kernel.org \
/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