linux-kernel - Re: [PATCH 1/2] dt-bindings: dma: Add reg-names to nvidia,tegra210-adma

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <918ca28c-2498-4c98-a257-33e828134087@kernel.org>
Date: Tue, 21 May 2024 11:24:39 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Sameer Pujar <spujar@...dia.com>, vkoul@...nel.org,
 thierry.reding@...il.com, dmaengine@...r.kernel.org
Cc: jonathanh@...dia.com, linux-tegra@...r.kernel.org,
 linux-kernel@...r.kernel.org, mkumard@...dia.com, ldewangan@...dia.com
Subject: Re: [PATCH 1/2] dt-bindings: dma: Add reg-names to
 nvidia,tegra210-adma

On 20/05/2024 14:23, Sameer Pujar wrote:
> From: Mohan Kumar <mkumard@...dia.com>
> 
> For Non-Hypervisor mode, Tegra ADMA driver requires the register
> resource range to include both global and channel page in the reg
> entry. For Hypervisor more, Tegra ADMA driver requires only the
> channel page and global page range is not allowed for access.
> 
> Add reg-names DT binding for Hypervisor mode to help driver to
> differentiate the config between Hypervisor and Non-Hypervisor
> mode of execution.
> 
> Signed-off-by: Mohan Kumar <mkumard@...dia.com>
> Signed-off-by: Sameer Pujar <spujar@...dia.com>

Please use scripts/get_maintainers.pl to get a list of necessary people
and lists to CC. It might happen, that command when run on an older
kernel, gives you outdated entries. Therefore please be sure you base
your patches on recent Linux kernel.

Tools like b4 or scripts/get_maintainer.pl provide you proper list of
people, so fix your workflow. Tools might also fail if you work on some
ancient tree (don't, instead use mainline), work on fork of kernel
(don't, instead use mainline) or you ignore some maintainers (really
don't). Just use b4 and everything should be fine, although remember
about `b4 prep --auto-to-cc` if you added new patches to the patchset.

You missed at least devicetree list (maybe more), so this won't be
tested by automated tooling. Performing review on untested code might be
a waste of time, thus I will skip this patch entirely till you follow
the process allowing the patch to be tested.

Please kindly resend and include all necessary To/Cc entries.

Best regards,
Krzysztof