From: Conor Dooley <conor@kernel.org>
To: Mark Tseng <chun-jen.tseng@mediatek.com>
Cc: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Philipp Zabel <p.zabel@pengutronix.de>,
Roger Lu <roger.lu@mediatek.com>,
Kevin Hilman <khilman@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org,
Project_Global_Chrome_Upstream_Group@mediatek.com
Subject: Re: [PATCH v1 3/3] dt-bindings: soc: mediatek: add mt8186 and mt8195 svs dt-bindings
Date: Wed, 11 Oct 2023 15:21:06 +0100 [thread overview]
Message-ID: <20231011-motor-equator-db141b74726a@spud> (raw)
In-Reply-To: <20231011034307.24641-4-chun-jen.tseng@mediatek.com>
[-- Attachment #1: Type: text/plain, Size: 312 bytes --]
On Wed, Oct 11, 2023 at 11:43:07AM +0800, Mark Tseng wrote:
> Add mt8186 and mt8195 svs compatible in dt-bindings.
This commit message just repeats the contexts of the diff in prose.
> Signed-off-by: Mark Tseng <chun-jen.tseng@mediatek.com>
Acked-by: Conor Dooley <conor.dooley@microchip.com>
Thanks,
Conor.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2023-10-11 14:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-11 3:43 [PATCH v1 0/3] soc: mediatek: svs: add support for MT8186 and MT8195 Mark Tseng
2023-10-11 3:43 ` [PATCH v1 1/3] soc: mediatek: svs: Add support for MT8195 SoC Mark Tseng
2023-11-16 9:01 ` AngeloGioacchino Del Regno
2023-10-11 3:43 ` [PATCH v1 2/3] soc: mediatek: svs: Add support for MT8186 SoC Mark Tseng
2023-11-16 9:01 ` AngeloGioacchino Del Regno
2023-10-11 3:43 ` [PATCH v1 3/3] dt-bindings: soc: mediatek: add mt8186 and mt8195 svs dt-bindings Mark Tseng
2023-10-11 14:21 ` Conor Dooley [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=20231011-motor-equator-db141b74726a@spud \
--to=conor@kernel.org \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=chun-jen.tseng@mediatek.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=khilman@kernel.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=matthias.bgg@gmail.com \
--cc=p.zabel@pengutronix.de \
--cc=robh+dt@kernel.org \
--cc=roger.lu@mediatek.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;
as well as URLs for NNTP newsgroup(s).