From: Jerome Brunet <jbrunet@baylibre.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Jian Hu <jian.hu@amlogic.com>,
Xianwei Zhao <xianwei.zhao@amlogic.com>,
Chuan Liu <chuan.liu@amlogic.com>,
Neil Armstrong <neil.armstrong@linaro.org>,
Kevin Hilman <khilman@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
robh+dt <robh+dt@kernel.org>, Rob Herring <robh@kernel.org>,
devicetree <devicetree@vger.kernel.org>,
linux-clk <linux-clk@vger.kernel.org>,
linux-amlogic <linux-amlogic@lists.infradead.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v6 2/5] dt-bindings: clock: add Amlogic T7 SCMI clock controller
Date: Thu, 11 Dec 2025 09:30:37 +0100 [thread overview]
Message-ID: <1j8qf92zf6.fsf@starbuckisacylon.baylibre.com> (raw)
In-Reply-To: <38ef7ee0-1879-42d5-a7fd-d32b96d01367@kernel.org> (Krzysztof Kozlowski's message of "Thu, 11 Dec 2025 07:16:25 +0100")
On Thu 11 Dec 2025 at 07:16, Krzysztof Kozlowski <krzk@kernel.org> wrote:
>>
>> Is there a new requirement to submit the DTS file changes along with the
>> driver changes now ?
>>
>> This has never been case before, especially since the changes are merged
>> through different trees.
>
> There is no such requirement, but "has never been case before" is
> clearly not accurate, because I raised this question multiple times last
> two-three years.
>
> There is no reasonable way to hold publishing of DTS, therefore if
> someone uses arguments like above with waiting for driver, I usually got
> suspicious.
>
> Also note, that many contributions from various people (not saying that
> this one here is) were bad quality and badly designed but without seeing
> DTS it takes me significantly more time to understand that design. So
> yes, publish your DTS solving all of the questions and making reviewing
> easier. Or don't and receive questions...
>
That's fair. Thanks for clarifying.
>
> Best regards,
> Krzysztof
--
Jerome
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next prev parent reply other threads:[~2025-12-11 8:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-04 5:36 [PATCH v6 0/5] add support for T7 family clock controller Jian Hu
2025-12-04 5:36 ` [PATCH v6 1/5] dt-bindings: clock: add Amlogic T7 PLL " Jian Hu
2025-12-04 5:36 ` [PATCH v6 2/5] dt-bindings: clock: add Amlogic T7 SCMI " Jian Hu
2025-12-08 6:17 ` Krzysztof Kozlowski
2025-12-08 8:40 ` Jian Hu
2025-12-09 6:01 ` Krzysztof Kozlowski
2025-12-09 10:16 ` Jerome Brunet
2025-12-11 6:16 ` Krzysztof Kozlowski
2025-12-11 8:30 ` Jerome Brunet [this message]
2025-12-04 5:36 ` [PATCH v6 3/5] dt-bindings: clock: add Amlogic T7 peripherals " Jian Hu
2025-12-04 5:36 ` [PATCH v6 4/5] clk: meson: t7: add support for the T7 SoC PLL clock Jian Hu
2025-12-06 3:18 ` kernel test robot
2025-12-04 5:36 ` [PATCH v6 5/5] clk: meson: t7: add t7 clock peripherals controller driver Jian Hu
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=1j8qf92zf6.fsf@starbuckisacylon.baylibre.com \
--to=jbrunet@baylibre.com \
--cc=chuan.liu@amlogic.com \
--cc=devicetree@vger.kernel.org \
--cc=jian.hu@amlogic.com \
--cc=khilman@baylibre.com \
--cc=krzk@kernel.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=neil.armstrong@linaro.org \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.org \
--cc=sboyd@kernel.org \
--cc=xianwei.zhao@amlogic.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