From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Peter Chen <peter.chen@cixtech.com>,
Krzysztof Kozlowski <krzk@kernel.org>
Cc: Marc Zyngier <maz@kernel.org>,
soc@kernel.org, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, catalin.marinas@arm.com, will@kernel.org,
arnd@arndb.de, linux-arm-kernel@lists.infradead.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
cix-kernel-upstream@cixtech.com, marcin@juszkiewicz.com.pl,
kajetan.puchalski@arm.com, Fugang Duan <fugang.duan@cixtech.com>
Subject: Re: [PATCH v5 5/6] arm64: dts: cix: add initial CIX P1(SKY1) dts support
Date: Thu, 27 Mar 2025 14:06:47 +0100 [thread overview]
Message-ID: <cba249f6-5552-4538-a2fc-4fcd185fefd0@linaro.org> (raw)
In-Reply-To: <Z-UeoIe4CPD3LwJv@nchen-desktop>
On 27/03/2025 10:47, Peter Chen wrote:
>>
>>>
>>> I thought we need to move one step and step before, and keep clean
>>> and avoid warning and error for every submission, but it seems not
>>> the way you prefer.
>>
>> No, from where did you get such impression? Maintainers-soc-clean-dts
>> explicitly covers this case and I WROTE IT, so how can I prefer
>> something else?
>>
>
> Krzysztof, I did not mean soc dts, I mean the mailbox binding checking
> warning which depends on this patch set.
>
> https://lore.kernel.org/lkml/174290730775.1655008.14031380406017771195.robh@kernel.org/
Ah, right, true and usual solution is:
https://www.kernel.org/doc/html/latest/process/maintainer-soc.html#submitting-patches-to-the-main-soc-maintainers
point 3, but heh, I am repeating myself.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-03-27 13:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-24 6:24 [PATCH v5 0/6] arm64: Introduce CIX P1 (SKY1) SoC Peter Chen
2025-03-24 6:24 ` [PATCH v5 1/6] dt-bindings: vendor-prefixes: Add CIX Technology Group Co., Ltd Peter Chen
2025-03-24 6:24 ` [PATCH v5 2/6] dt-bindings: arm: add CIX P1 (SKY1) SoC Peter Chen
2025-03-24 6:24 ` [PATCH v5 3/6] arm64: Kconfig: add ARCH_CIX for cix silicons Peter Chen
2025-03-24 6:24 ` [PATCH v5 4/6] arm64: defconfig: Enable CIX SoC Peter Chen
2025-03-24 6:24 ` [PATCH v5 5/6] arm64: dts: cix: add initial CIX P1(SKY1) dts support Peter Chen
2025-03-25 10:52 ` Marc Zyngier
2025-03-26 3:26 ` Peter Chen
2025-03-26 9:12 ` Marc Zyngier
2025-03-27 6:44 ` Peter Chen
2025-03-27 7:16 ` Krzysztof Kozlowski
2025-03-27 8:18 ` Arnd Bergmann
2025-03-27 9:31 ` Peter Chen
2025-03-27 10:29 ` Arnd Bergmann
2025-03-27 8:35 ` Peter Chen
2025-03-27 8:40 ` Krzysztof Kozlowski
2025-03-27 9:47 ` Peter Chen
2025-03-27 13:06 ` Krzysztof Kozlowski [this message]
2025-03-24 6:24 ` [PATCH v5 6/6] MAINTAINERS: Add CIX SoC maintainer entry Peter Chen
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=cba249f6-5552-4538-a2fc-4fcd185fefd0@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=cix-kernel-upstream@cixtech.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=fugang.duan@cixtech.com \
--cc=kajetan.puchalski@arm.com \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcin@juszkiewicz.com.pl \
--cc=maz@kernel.org \
--cc=peter.chen@cixtech.com \
--cc=robh@kernel.org \
--cc=soc@kernel.org \
--cc=will@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®