From: Krzysztof Kozlowski <krzk@kernel.org>
To: "irving.ch.lin" <irving-ch.lin@mediatek.com>,
Wim Van Sebroeck <wim@linux-watchdog.org>,
Guenter Roeck <linux@roeck-us.net>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Philipp Zabel <p.zabel@pengutronix.de>,
nfraprado@collabora.com
Cc: angelogioacchino.delregno@collabora.com,
Project_Global_Chrome_Upstream_Group@mediatek.com,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org,
linux-pm@vger.kernel.org, netdev@vger.kernel.org,
linux-mediatek@lists.infradead.org,
Irving lin <irving-ch.lin@mediatek.corp-partner.google.com>
Subject: Re: clk: mt8189: Porting driver for clk
Date: Mon, 2 Jun 2025 11:16:19 +0200 [thread overview]
Message-ID: <9b54c25e-27e9-4590-9ba4-030ba485abcc@kernel.org> (raw)
In-Reply-To: <20250602082610.1848291-1-irving-ch.lin@mediatek.com>
On 02/06/2025 10:25, irving.ch.lin wrote:
> From: Irving lin <irving-ch.lin@mediatek.corp-partner.google.com>
>
> 1. Add mt8189 clk driver
> 2. Fix mux failed
> 3. Add apll12_div_tdmout_b
> 4. Add disable-unused configs
>
> BUG=b:387252012
> TEST=emerge-skywalker chromeos-kernel-6_6
6_6 feels like v6.6, so nope. You need to start working on mainline and
TESTING on mainline.
This also explains a bit all the issues which you copied from downstream
drivers... although they were fixed in v6.6 as well, so maybe not. :/
Best regards,
Krzysztof
prev parent reply other threads:[~2025-06-02 9:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-02 8:25 clk: mt8189: Porting driver for clk irving.ch.lin
2025-06-02 8:33 ` Krzysztof Kozlowski
2025-06-02 9:16 ` 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=9b54c25e-27e9-4590-9ba4-030ba485abcc@kernel.org \
--to=krzk@kernel.org \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=irving-ch.lin@mediatek.com \
--cc=irving-ch.lin@mediatek.corp-partner.google.com \
--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=linux-mediatek@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=matthias.bgg@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=nfraprado@collabora.com \
--cc=p.zabel@pengutronix.de \
--cc=robh+dt@kernel.org \
--cc=wim@linux-watchdog.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).