Re: [PATCH v13 1/3] dt-bindings: perf: Add Broadcom Raspberry Pi AXI PMU definition

[Krzysztof Kozlowski <krzk@kernel.org>]

On 15/08/2026 19:27, Ian Rogers wrote:
> Add Device Tree bindings for the Broadcom AXI PMU hardware blocks present
> in the Raspberry Pi SoC line (BCM2835, BCM2711, BCM2712).
> 
> Depending on the SoC and security configuration, these PMUs support either
> direct MMIO access or routing via the Raspberry Pi firmware Mailbox IPC.
> The bindings support defining 1 or 2 backing MMIO regions natively map
> the system and VPU control surfaces.
> 
> Assisted-by: Antigravity:gemini-3.6-flash
> Signed-off-by: Ian Rogers <irogers@google.com>

What is this mess thread of 13 versions tied together? And still none of
them are actually sent to maintainers?


Do not attach (thread) your patchsets to some other threads (unrelated
or older versions). This buries them deep in the mailbox and might
interfere with applying entire sets. See also:
https://elixir.bootlin.com/linux/v6.16-rc2/source/Documentation/process/submitting-patches.rst#L830
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) or work on fork of kernel
(don't, instead use mainline). 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.

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


Best regards,
Krzysztof