From: Matthias Brugger <matthias.bgg@gmail.com>
To: "allen-kh.cheng" <allen-kh.cheng@mediatek.com>,
Rob Herring <robh+dt@kernel.org>,
nfraprado@collabora.com
Cc: Project_Global_Chrome_Upstream_Group@mediatek.com,
chun-jie.chen@mediatek.com, devicetree@vger.kernel.org,
drinkcat@chromium.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org,
srv_heupstream@mediatek.com, Chen-Yu Tsai <wenst@chromium.org>,
Ryder Lee <ryder.lee@kernel.org>
Subject: Re: [PATCH v3 0/5] Update MT8192 Clock Setting
Date: Wed, 12 Jan 2022 17:51:23 +0100 [thread overview]
Message-ID: <d36d276a-c3be-431b-3636-c313cabda3d4@gmail.com> (raw)
In-Reply-To: <20220112115542.10606-1-allen-kh.cheng@mediatek.com>
On 12/01/2022 12:55, allen-kh.cheng wrote:
> From: Allen-KH Cheng <Allen-KH.Cheng@mediatek.com>
>
> This patch is base on v5.16-rc8,
> series "Mediatek MT8192 clock support"[1], [2] annd [3].
> [1] https://patchwork.kernel.org/project/linux-mediatek/list/?series=521127
> [2] https://patchwork.kernel.org/project/linux-mediatek/patch/20210727023205.20319-2-chun-jie.chen@mediatek.com/
> [3] https://lore.kernel.org/all/20210825011120.30481-1-chun-jie.chen@mediatek.com/
Please update that list to only who the patches that are not yet upstream. That
will help me to understand if I can take them right now or if we have to wait
for something to get applied first.
Thanks,
Matthias
>
> changes since v2:
> - add missing "clock" at the end of commit message
>
> changes since v1:
> - update the commit message
>
> Allen-KH Cheng (5):
> arm64: dts: mediatek: Correct uart clock of MT8192
> arm64: dts: mediatek: Correct SPI clock of MT8192
> arm64: dts: mediatek: Correct Nor Flash clock of MT8192
> arm64: dts: mediatek: Correct I2C clock of MT8192
> arm64: dts: mediatek: Correct system timer clock of MT8192
>
> arch/arm64/boot/dts/mediatek/mt8192.dtsi | 92 +++++++++++++-----------
> 1 file changed, 52 insertions(+), 40 deletions(-)
>
parent reply other threads:[~2022-01-12 16:51 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20220112115542.10606-1-allen-kh.cheng@mediatek.com>]
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=d36d276a-c3be-431b-3636-c313cabda3d4@gmail.com \
--to=matthias.bgg@gmail.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=allen-kh.cheng@mediatek.com \
--cc=chun-jie.chen@mediatek.com \
--cc=devicetree@vger.kernel.org \
--cc=drinkcat@chromium.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=nfraprado@collabora.com \
--cc=robh+dt@kernel.org \
--cc=ryder.lee@kernel.org \
--cc=srv_heupstream@mediatek.com \
--cc=wenst@chromium.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
Powered by JetHome