From: Krzysztof Kozlowski <krzk@kernel.org>
To: j0sh1x <aljoshua.hell@gmail.com>, tglx@kernel.org
Cc: linux-kernel@vger.kernel.org, subsystem@vger.kernel.org,
dominikkobinski314@gmail.com
Subject: Re: [PATCH 1/5] dt-bindings: irq: Add Qualcomm MSM VIC binding
Date: Mon, 16 Mar 2026 09:29:13 +0100 [thread overview]
Message-ID: <437326d8-6b29-4426-8f5f-3251c3e9e91d@kernel.org> (raw)
In-Reply-To: <20260315111705.118544-1-aljoshua.hell@gmail.com>
On 15/03/2026 12:17, j0sh1x wrote:
> Signed-off-by: j0sh1x <aljoshua.hell@gmail.com>
Please run scripts/checkpatch.pl on the patches and fix reported
warnings. After that, run also 'scripts/checkpatch.pl --strict' on the
patches and (probably) fix more warnings. Some warnings can be ignored,
especially from --strict run, but the code here looks like it needs a
fix. Feel free to get in touch if the warning is not clear.
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.
> ---
> .../interrupt-controller/qcom,msm-vic.yaml | 72 +++++++++++++++++++
> 1 file changed, 72 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/interrupt-controller/qcom,msm-vic.yaml
>
> diff --git a/Documentation/devicetree/bindings/interrupt-controller/qcom,msm-vic.yaml b/Documentation/devicetree/bindings/interrupt-controller/qcom,msm-vic.yaml
> new file mode 100644
> index 000000000000..5bf281f72fe0
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/interrupt-controller/qcom,msm-vic.yaml
> @@ -0,0 +1,72 @@
> +# SPDX-License-Identifier: GPL-2.0
> +# qualcomm,msm-vic.yaml - Device Tree binding for Qualcomm MSM VIC interrupt controller
> +
> +description: >
> + Qualcomm MSM VIC (Vector Interrupt Controller). This interrupt controller
> + handles normal and wakeup interrupts and supports mapping to the
> + Qualcomm SMSM system.
> +
> +compatible: ["qcom,msm-vic"]
> +
> +properties:
> + interrupt-controller:
> + description: "Identifies this node as an interrupt controller"
> + required: true
> + type: boolean
> +
> + #interrupt-cells:
> + description: "Specifies the number of cells needed to encode an interrupt"
> + required: true
> + type: integer
> + default: 1
I don't know what you wrote, but this is not a DT binding. Don't send us
LLM microslop products. Read first docs guiding you what you have to do.
Also, nothing here was tested.
NAK
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-03-16 8:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-15 11:17 j0sh1x
2026-03-15 11:17 ` [PATCH 2/5] irqchip: Add Qualcomm MSM VIC driver j0sh1x
2026-03-16 8:30 ` Krzysztof Kozlowski
2026-03-20 9:51 ` Thomas Gleixner
2026-03-15 11:17 ` [PATCH 3/5] irqchip: Add Kconfig and Makefile entries for MSM VIC j0sh1x
2026-03-30 4:45 ` kernel test robot
2026-03-30 9:04 ` kernel test robot
2026-03-15 11:17 ` [PATCH 4/5] dt-bindings: irq: Add Qualcomm MSM VIC header j0sh1x
2026-03-16 8:30 ` Krzysztof Kozlowski
2026-03-15 11:17 ` [PATCH 5/5] MAINTAINERS: Add Maintainer entry for MSM VIC j0sh1x
2026-03-16 8:29 ` Krzysztof Kozlowski [this message]
2026-03-16 17:56 ` [PATCH 1/5] dt-bindings: irq: Add Qualcomm MSM VIC binding Krzysztof Kozlowski
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=437326d8-6b29-4426-8f5f-3251c3e9e91d@kernel.org \
--to=krzk@kernel.org \
--cc=aljoshua.hell@gmail.com \
--cc=dominikkobinski314@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=subsystem@vger.kernel.org \
--cc=tglx@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
all inboxes | Powered by JetHome®