From: Krzysztof Kozlowski <krzk@kernel.org>
To: Vladimir Kondratiev <vladimir.kondratiev@mobileye.com>,
Anup Patel <anup@brainfault.org>,
Thomas Gleixner <tglx@linutronix.de>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: interrupt-controller: add risc-v,aplic hart indexes
Date: Thu, 2 Jan 2025 17:10:17 +0100 [thread overview]
Message-ID: <b69a88f7-0b72-4cd9-8e5d-d28db2e20444@kernel.org> (raw)
In-Reply-To: <20250102094116.3847894-2-vladimir.kondratiev@mobileye.com>
On 02/01/2025 10:41, Vladimir Kondratiev wrote:
> Document optional property "riscv,hart-index"
>
> Signed-off-by: Vladimir Kondratiev <vladimir.kondratiev@mobileye.com>
<form letter>
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.
</form letter>
Best regards,
Krzysztof
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2025-01-02 16:10 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-02 9:41 [PATCH 0/2] riscv,aplic: support for hart indexes Vladimir Kondratiev
2025-01-02 9:41 ` [PATCH 1/2] dt-bindings: interrupt-controller: add risc-v,aplic " Vladimir Kondratiev
2025-01-02 15:20 ` Anup Patel
2025-01-02 16:10 ` Krzysztof Kozlowski [this message]
2025-01-07 8:59 ` Vladimir Kondratiev
2025-01-02 9:41 ` [PATCH 2/2] irqchip/riscv-aplic: add support for " Vladimir Kondratiev
2025-01-02 15:54 ` Anup Patel
2025-01-05 8:12 ` Vladimir Kondratiev
2025-01-05 8:39 ` [PATCH v2] " Vladimir Kondratiev
2025-01-06 16:22 ` Anup Patel
2025-01-07 7:58 ` [PATCH v3 0/2] riscv,aplic: " Vladimir Kondratiev
2025-01-07 7:58 ` [PATCH v3 1/2] dt-bindings: interrupt-controller: add risc-v,aplic " Vladimir Kondratiev
2025-01-08 12:25 ` Anup Patel
2025-01-09 7:56 ` Krzysztof Kozlowski
2025-01-09 9:13 ` Vladimir Kondratiev
2025-01-10 7:46 ` Krzysztof Kozlowski
2025-01-07 7:58 ` [PATCH v3 2/2] irqchip/riscv-aplic: add support for " Vladimir Kondratiev
2025-01-08 12:27 ` Anup Patel
2025-01-02 12:48 ` [PATCH 0/2] riscv,aplic: " Anup Patel
2025-01-02 14:01 ` Vladimir Kondratiev
2025-01-02 14:41 ` Anup Patel
2025-01-02 15:07 ` Vladimir Kondratiev
2025-01-02 15:19 ` Anup Patel
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=b69a88f7-0b72-4cd9-8e5d-d28db2e20444@kernel.org \
--to=krzk@kernel.org \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=conor+dt@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=robh@kernel.org \
--cc=tglx@linutronix.de \
--cc=vladimir.kondratiev@mobileye.com \
/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