From: Matthias Brugger <matthias.bgg@gmail.com>
To: Allen-KH Cheng <allen-kh.cheng@mediatek.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Stephen Boyd <sboyd@kernel.org>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>
Cc: Project_Global_Chrome_Upstream_Group@mediatek.com,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org,
hsinyi@chromium.org
Subject: Re: [PATCH v5 0/6] Add and update some driver nodes for MT8186 SoC
Date: Mon, 29 May 2023 15:46:04 +0200 [thread overview]
Message-ID: <ec70aecd-3229-ee5f-1375-1a116a1f6213@gmail.com> (raw)
In-Reply-To: <20230324021258.15863-1-allen-kh.cheng@mediatek.com>
On 24/03/2023 03:12, Allen-KH Cheng wrote:
> This series is based on linux for-next.
>
> Changes since v4:
> - compress the compatible strings for display nodes
>
> Changes since v3:
> - Add index for ovl in aliases
>
> Changes since v2:
> - Remove some unnecessary linebreaks for some nodes
> - Use one line for some properties
> - Drop "Fix the fallback for mediatek, mt8186-disp-ccorr" patch
> (since this is applied in chunkuang.hu/linux.git/log/?h=mediatek-drm-next)
> - Separate GCE into another patch
> - Drop some patches which are appied in matthias github
>
> Changes since v1:
> - Remove the unnecessary trailing number
> - Add aliases for ovl* and rdma*
>
> Allen-KH Cheng (6):
> arm64: dts: mediatek: mt8186: Add MTU3 nodes
> dt-bindings: spmi: spmi-mtk-pmif: Document mediatek,mt8195-spmi as
> fallback of mediatek,mt8186-spmi
> arm64: dts: mediatek: mt8186: Add SPMI node
> arm64: dts: mediatek: mt8186: Add ADSP node
> arm64: dts: mediatek: mt8186: Add GCE node
> arm64: dts: mediatek: mt8186: Add display nodes
>
> .../bindings/spmi/mtk,spmi-mtk-pmif.yaml | 11 +-
> arch/arm64/boot/dts/mediatek/mt8186.dtsi | 225 ++++++++++++++++++
> 2 files changed, 233 insertions(+), 3 deletions(-)
>
Whole series applied, thanks!
prev parent reply other threads:[~2023-05-29 13:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-24 2:12 [PATCH v5 0/6] Add and update some driver nodes for MT8186 SoC Allen-KH Cheng
2023-03-24 2:12 ` [PATCH v5 1/6] arm64: dts: mediatek: mt8186: Add MTU3 nodes Allen-KH Cheng
2023-05-29 13:42 ` Matthias Brugger
2023-03-24 2:12 ` [PATCH v5 2/6] dt-bindings: spmi: spmi-mtk-pmif: Document mediatek,mt8195-spmi as fallback of mediatek,mt8186-spmi Allen-KH Cheng
2023-03-24 2:12 ` [PATCH v5 3/6] arm64: dts: mediatek: mt8186: Add SPMI node Allen-KH Cheng
2023-03-24 2:12 ` [PATCH v5 4/6] arm64: dts: mediatek: mt8186: Add ADSP node Allen-KH Cheng
2023-03-24 2:12 ` [PATCH v5 5/6] arm64: dts: mediatek: mt8186: Add GCE node Allen-KH Cheng
2023-03-24 2:12 ` [PATCH v5 6/6] arm64: dts: mediatek: mt8186: Add display nodes Allen-KH Cheng
2023-04-14 1:27 ` [PATCH v5 0/6] Add and update some driver nodes for MT8186 SoC Allen-KH Cheng (程冠勳)
2023-05-29 13:46 ` Matthias Brugger [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=ec70aecd-3229-ee5f-1375-1a116a1f6213@gmail.com \
--to=matthias.bgg@gmail.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=allen-kh.cheng@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=hsinyi@chromium.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--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).