From: Krzysztof Kozlowski <krzk@kernel.org>
To: E Shattow <e@freeshell.de>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
Abel Vesa <abelvesa@kernel.org>, Peng Fan <peng.fan@nxp.com>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>
Cc: Marek Vasut <marek.vasut+renesas@mailbox.org>,
devicetree@vger.kernel.org, imx@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org
Subject: Re: [PATCH v1] dts: arm64: freescale: move imx9*-clock.h imx9*-power.h into dt-bindings
Date: Mon, 1 Sep 2025 05:32:55 +0200 [thread overview]
Message-ID: <d802bcea-d81f-49eb-96ce-5d89dddca7c3@kernel.org> (raw)
In-Reply-To: <20250831200516.522179-1-e@freeshell.de>
On 31/08/2025 22:04, E Shattow wrote:
> Move imx9*-{clock,power}.h headers into
> include/dt-bindings/{clock,power}/ and fix up the DTs
Huh? Why?
>
> Reported-by: Marek Vasut <marek.vasut+renesas@mailbox.org>
What sort of bug are you fixing? Nothing in commit msg explains that at all.
> Signed-off-by: E Shattow <e@freeshell.de>
Best regards,
Krzysztof
prev parent reply other threads:[~2025-09-01 3:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-31 20:04 [PATCH v1] dts: arm64: freescale: move imx9*-clock.h imx9*-power.h into dt-bindings E Shattow
2025-09-01 3:22 ` Peng Fan
2025-09-01 2:22 ` Marek Vasut
2025-09-01 3:33 ` Krzysztof Kozlowski
2025-09-01 6:09 ` Peng Fan
2025-09-01 10:30 ` Marek Vasut
2025-09-01 10:54 ` Krzysztof Kozlowski
2025-09-01 11:07 ` E Shattow
2025-09-01 12:15 ` Krzysztof Kozlowski
2025-09-01 23:32 ` Marek Vasut
2025-09-04 9:34 ` Peng Fan
2025-09-08 23:39 ` Marek Vasut
2025-09-10 7:07 ` Peng Fan
2025-10-02 5:27 ` E Shattow
2025-11-02 17:42 ` Marek Vasut
2025-09-01 3:32 ` Krzysztof Kozlowski [this message]
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=d802bcea-d81f-49eb-96ce-5d89dddca7c3@kernel.org \
--to=krzk@kernel.org \
--cc=abelvesa@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=e@freeshell.de \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marek.vasut+renesas@mailbox.org \
--cc=mturquette@baylibre.com \
--cc=peng.fan@nxp.com \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=sboyd@kernel.org \
--cc=shawnguo@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.