From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: "Garmin Chang (張家銘)" <Garmin.Chang@mediatek.com>,
"matthias.bgg@gmail.com" <matthias.bgg@gmail.com>,
"sboyd@kernel.org" <sboyd@kernel.org>,
"mturquette@baylibre.com" <mturquette@baylibre.com>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"krzysztof.kozlowski+dt@linaro.org"
<krzysztof.kozlowski+dt@linaro.org>,
"richardcochran@gmail.com" <richardcochran@gmail.com>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mediatek@lists.infradead.org"
<linux-mediatek@lists.infradead.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-clk@vger.kernel.org" <linux-clk@vger.kernel.org>,
Project_Global_Chrome_Upstream_Group
<Project_Global_Chrome_Upstream_Group@mediatek.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH v3 01/19] dt-bindings: ARM: MediaTek: Add new document bindings of MT8188 clock
Date: Mon, 9 Jan 2023 11:31:51 +0100 [thread overview]
Message-ID: <2e52c0a5-3578-c90f-f54e-8cc29f6699a9@linaro.org> (raw)
In-Reply-To: <df20ff7bf661b021d5917956af08883f3b9657e0.camel@mediatek.com>
On 09/01/2023 11:14, Garmin Chang (張家銘) wrote:
>>> b/Documentation/devicetree/bindings/arm/mediatek/mediatek,mt8188-
>>> clock.yaml
>>
>> Clock controllers do not go to arm but to clock. It's so suprising
>> directory that I missed to notice it in v1... Why putting it in some
>> totally irrelevant directory?
>>
> Do you mean move to the path below ?
> Documentation\devicetree\bindings\clock
>
> If yes, I will change it in v4.
Yes.
Best regards,
Krzysztof
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-01-09 10:33 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-30 7:33 [PATCH v3 00/19] MediaTek MT8188 clock support Garmin.Chang
2022-12-30 7:33 ` [PATCH v3 01/19] dt-bindings: ARM: MediaTek: Add new document bindings of MT8188 clock Garmin.Chang
2022-12-30 10:41 ` Krzysztof Kozlowski
2023-01-09 10:14 ` Garmin Chang (張家銘)
2023-01-09 10:31 ` Krzysztof Kozlowski [this message]
2022-12-30 7:33 ` [PATCH v3 02/19] clk: mediatek: Add MT8188 apmixedsys clock support Garmin.Chang
2022-12-30 7:33 ` [PATCH v3 03/19] clk: mediatek: Add MT8188 topckgen " Garmin.Chang
2022-12-30 7:33 ` [PATCH v3 04/19] clk: mediatek: Add MT8188 peripheral " Garmin.Chang
2022-12-30 7:33 ` [PATCH v3 05/19] clk: mediatek: Add MT8188 infrastructure " Garmin.Chang
2022-12-30 7:33 ` [PATCH v3 06/19] clk: mediatek: Add MT8188 camsys " Garmin.Chang
2022-12-30 7:33 ` [PATCH v3 07/19] clk: mediatek: Add MT8188 ccusys " Garmin.Chang
2022-12-30 7:33 ` [PATCH v3 08/19] clk: mediatek: Add MT8188 imgsys " Garmin.Chang
2022-12-30 7:33 ` [PATCH v3 09/19] clk: mediatek: Add MT8188 ipesys " Garmin.Chang
2022-12-30 7:33 ` [PATCH v3 10/19] clk: mediatek: Add MT8188 mfgcfg " Garmin.Chang
2022-12-30 7:33 ` [PATCH v3 11/19] clk: mediatek: Add MT8188 vdecsys " Garmin.Chang
2022-12-30 7:33 ` [PATCH v3 12/19] clk: mediatek: Add MT8188 vdosys0 " Garmin.Chang
2022-12-30 7:33 ` [PATCH v3 13/19] clk: mediatek: Add MT8188 vdosys1 " Garmin.Chang
2022-12-30 7:33 ` [PATCH v3 14/19] clk: mediatek: Add MT8188 vencsys " Garmin.Chang
2022-12-30 7:33 ` [PATCH v3 15/19] clk: mediatek: Add MT8188 vppsys0 " Garmin.Chang
2022-12-30 7:33 ` [PATCH v3 16/19] clk: mediatek: Add MT8188 vppsys1 " Garmin.Chang
2022-12-30 7:33 ` [PATCH v3 17/19] clk: mediatek: Add MT8188 wpesys " Garmin.Chang
2022-12-30 7:33 ` [PATCH v3 18/19] clk: mediatek: Add MT8188 imp i2c wrapper " Garmin.Chang
2022-12-30 7:33 ` [PATCH v3 19/19] clk: mediatek: Add MT8188 adsp " Garmin.Chang
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=2e52c0a5-3578-c90f-f54e-8cc29f6699a9@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=Garmin.Chang@mediatek.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=mturquette@baylibre.com \
--cc=netdev@vger.kernel.org \
--cc=richardcochran@gmail.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@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;
as well as URLs for NNTP newsgroup(s).