[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5d6b6314-c3f8-412f-850b-651365af4b4c@kernel.org>
Date: Fri, 26 Apr 2024 14:22:10 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Robert Nelson <robertcnelson@...il.com>,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
devicetree@...r.kernel.org
Cc: Rob Herring <robh@...nel.org>, Andrew Davis <afd@...com>,
Nishanth Menon <nm@...com>, Jared McArthur <j-mcarthur@...com>,
Jason Kridner <jkridner@...gleboard.org>,
Deepak Khatri <lorforlinux@...gleboard.org>,
Drew Fustini <drew@...gleboard.org>
Subject: Re: [PATCH v2 1/2] dt-bindings: arm: ti: Add BeagleY-AI
On 25/04/2024 18:28, Robert Nelson wrote:
> This board is based on ti,j722s family using the am67a variation.
>
> https://beagley-ai.org/
> https://openbeagle.org/beagley-ai/beagley-ai
>
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
Powered by blists - more mailing lists