From: "Stefan Dösinger" <stefandoesinger@gmail.com>
To: Lee Jones <lee@kernel.org>
Cc: Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Philipp Zabel <p.zabel@pengutronix.de>,
Brian Masney <bmasney@redhat.com>, Vinod Koul <vkoul@kernel.org>,
Neil Armstrong <neil.armstrong@linaro.org>,
Russell King <linux@armlinux.org.uk>,
Brian Masney <bmasney+clk@redhat.com>,
Jerome Brunet <jbrunet+clk@baylibre.com>,
Manivannan Sadhasivam <mani@kernel.org>,
linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-phy@lists.infradead.org, mfd@lists.linux.dev
Subject: Re: [PATCH v13 04/13] mfd: zx297520v3: Add a clock and reset MFD driver
Date: Fri, 16 Oct 2026 09:20:09 +0200 [thread overview]
Message-ID: <D_WXy70pRh6G3mLeAQ5LsQ@gmail.com> (raw)
In-Reply-To: <179198492486.839288.18023026004912443161@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 1235 bytes --]
Am Donnerstag, 15. Oktober 2026, 17:34:06 Mitteleuropäische Sommerzeit schrieb
Lee Jones:
> --- checkpatch.pl (3 issues) ---
> Line 227: WARNING: DT compatible string "zte,zx297520v3-topcrm" appears
> un-documented -- check ./Documentation/devicetree/bindings/ Line 228:
> WARNING: DT compatible string "zte,zx297520v3-matrixcrm" appears
> un-documented -- check ./Documentation/devicetree/bindings/ Line 229:
> WARNING: DT compatible string "zte,zx297520v3-lspcrm" appears un-documented
> -- check ./Documentation/devicetree/bindings/
> ----------------------------------
>
> Is Checkpatch right?
No and yes - the bindings were the first 3 patches of my series. Since you are
cherry-picking the mfd patch only, the bindings will obviously be missing.
The bindings got merged into the clk tree and made their way into Linux-next
already. I guess we can either ignore checkpatch and the issue will resolve
itself when the trees are merged together or I resubmit the mfd patch when the
bindings made their way into kernel/git/lee/mfd.git . At that point I can also
re-add the MAINTAINERS change and it should apply without conflict.
I am still fairly new to this - is there an option or issue I missed?
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 870 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: "Stefan Dösinger" <stefandoesinger@gmail.com>
To: Lee Jones <lee@kernel.org>
Cc: Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Philipp Zabel <p.zabel@pengutronix.de>,
Brian Masney <bmasney@redhat.com>, Vinod Koul <vkoul@kernel.org>,
Neil Armstrong <neil.armstrong@linaro.org>,
Russell King <linux@armlinux.org.uk>,
Brian Masney <bmasney+clk@redhat.com>,
Jerome Brunet <jbrunet+clk@baylibre.com>,
Manivannan Sadhasivam <mani@kernel.org>,
linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-phy@lists.infradead.org, mfd@lists.linux.dev
Subject: Re: [PATCH v13 04/13] mfd: zx297520v3: Add a clock and reset MFD driver
Date: Fri, 16 Oct 2026 09:20:09 +0200 [thread overview]
Message-ID: <D_WXy70pRh6G3mLeAQ5LsQ@gmail.com> (raw)
In-Reply-To: <179198492486.839288.18023026004912443161@kernel.org>
[-- Attachment #1.1: Type: text/plain, Size: 1235 bytes --]
Am Donnerstag, 15. Oktober 2026, 17:34:06 Mitteleuropäische Sommerzeit schrieb
Lee Jones:
> --- checkpatch.pl (3 issues) ---
> Line 227: WARNING: DT compatible string "zte,zx297520v3-topcrm" appears
> un-documented -- check ./Documentation/devicetree/bindings/ Line 228:
> WARNING: DT compatible string "zte,zx297520v3-matrixcrm" appears
> un-documented -- check ./Documentation/devicetree/bindings/ Line 229:
> WARNING: DT compatible string "zte,zx297520v3-lspcrm" appears un-documented
> -- check ./Documentation/devicetree/bindings/
> ----------------------------------
>
> Is Checkpatch right?
No and yes - the bindings were the first 3 patches of my series. Since you are
cherry-picking the mfd patch only, the bindings will obviously be missing.
The bindings got merged into the clk tree and made their way into Linux-next
already. I guess we can either ignore checkpatch and the issue will resolve
itself when the trees are merged together or I resubmit the mfd patch when the
bindings made their way into kernel/git/lee/mfd.git . At that point I can also
re-add the MAINTAINERS change and it should apply without conflict.
I am still fairly new to this - is there an option or issue I missed?
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 870 bytes --]
[-- Attachment #2: Type: text/plain, Size: 112 bytes --]
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
next prev parent reply other threads:[~2026-10-16 7:20 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-27 20:13 [PATCH v13 00/13] ZTE zx297520v3 clock bindings and driver Stefan Dösinger
2026-09-27 20:13 ` Stefan Dösinger
2026-09-27 20:13 ` [PATCH v13 01/13] dt-bindings: clk: zte: Add zx297520v3 top clock and reset controller Stefan Dösinger
2026-09-27 20:13 ` Stefan Dösinger
2026-09-27 20:54 ` sashiko-bot
2026-09-27 20:54 ` sashiko-bot
2026-09-27 20:13 ` [PATCH v13 03/13] dt-bindings: clk: zte: Add zx297520v3 LSP " Stefan Dösinger
2026-09-27 20:13 ` Stefan Dösinger
2026-09-27 20:54 ` sashiko-bot
2026-09-27 20:54 ` sashiko-bot
2026-09-27 20:13 ` [PATCH v13 04/13] mfd: zx297520v3: Add a clock and reset MFD driver Stefan Dösinger
2026-09-27 20:13 ` Stefan Dösinger
2026-09-27 20:57 ` sashiko-bot
2026-09-27 20:57 ` sashiko-bot
2026-10-15 15:34 ` Lee Jones
2026-10-15 15:34 ` Lee Jones
2026-10-16 7:20 ` Stefan Dösinger [this message]
2026-10-16 7:20 ` Stefan Dösinger
2026-10-20 11:57 ` Lee Jones
2026-10-20 11:57 ` Lee Jones
2026-09-27 20:13 ` [PATCH v13 05/13] Maintainers: Add entry for drivers/mfd/zte-zx297520v3-crm.c Stefan Dösinger
2026-09-27 20:13 ` Stefan Dösinger
2026-09-27 20:13 ` [PATCH v13 06/13] clk: zte: Add Clock registration infrastructure Stefan Dösinger
2026-09-27 20:13 ` Stefan Dösinger
2026-09-27 20:59 ` sashiko-bot
2026-09-27 20:59 ` sashiko-bot
2026-09-27 20:13 ` [PATCH v13 07/13] clk: zte: Add regmap-based clocks Stefan Dösinger
2026-09-27 20:13 ` Stefan Dösinger
2026-09-27 20:59 ` sashiko-bot
2026-09-27 20:59 ` sashiko-bot
2026-09-27 20:13 ` [PATCH v13 08/13] clk: zte: Add zx PLL support infrastructure Stefan Dösinger
2026-09-27 20:13 ` Stefan Dösinger
2026-09-27 21:00 ` sashiko-bot
2026-09-27 21:00 ` sashiko-bot
2026-09-27 20:13 ` [PATCH v13 09/13] clk: zte: Introduce a driver for zx297520v3 top clocks Stefan Dösinger
2026-09-27 20:13 ` Stefan Dösinger
2026-09-27 21:00 ` sashiko-bot
2026-09-27 21:00 ` sashiko-bot
2026-09-27 20:13 ` [PATCH v13 10/13] clk: zte: Introduce a driver for zx297520v3 matrix clocks Stefan Dösinger
2026-09-27 20:13 ` Stefan Dösinger
2026-09-27 21:05 ` sashiko-bot
2026-09-27 21:05 ` sashiko-bot
2026-09-27 20:13 ` [PATCH v13 11/13] clk: zte: Introduce a driver for zx297520v3 LSP clocks Stefan Dösinger
2026-09-27 20:13 ` Stefan Dösinger
2026-09-27 20:58 ` sashiko-bot
2026-09-27 20:58 ` sashiko-bot
2026-09-27 20:13 ` [PATCH v13 12/13] reset: zte: Add a zx297520v3 reset driver Stefan Dösinger
2026-09-27 20:13 ` Stefan Dösinger
2026-09-27 20:59 ` sashiko-bot
2026-09-27 20:59 ` sashiko-bot
2026-09-27 20:13 ` [PATCH v13 13/13] ARM: dts: zte: Declare zx297520v3 CRM device nodes Stefan Dösinger
2026-09-27 20:13 ` Stefan Dösinger
2026-09-27 20:57 ` sashiko-bot
2026-09-27 20:57 ` sashiko-bot
2026-09-27 20:50 ` [PATCH v13 02/13] dt-bindings: clk: zte: Add zx297520v3 matrix clock and reset controller Stefan Dösinger
2026-09-27 20:50 ` Stefan Dösinger
2026-09-27 20:54 ` sashiko-bot
2026-09-27 20:54 ` sashiko-bot
2026-10-02 15:08 ` (subset) [PATCH v13 00/13] ZTE zx297520v3 clock bindings and driver Brian Masney
2026-10-02 15:08 ` Brian Masney
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=D_WXy70pRh6G3mLeAQ5LsQ@gmail.com \
--to=stefandoesinger@gmail.com \
--cc=bmasney+clk@redhat.com \
--cc=bmasney@redhat.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jbrunet+clk@baylibre.com \
--cc=krzk+dt@kernel.org \
--cc=lee@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--cc=mani@kernel.org \
--cc=mfd@lists.linux.dev \
--cc=mturquette@baylibre.com \
--cc=neil.armstrong@linaro.org \
--cc=p.zabel@pengutronix.de \
--cc=robh@kernel.org \
--cc=sboyd@kernel.org \
--cc=vkoul@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.