From: Elvis.Wang <Elvis.Wang@mediatek.com>
To: Jassi Brar <jassisinghbrar@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
Elvis Wang <Elvis.Wang@mediatek.com>
Cc: "jason-jh . lin" <jason-jh.lin@mediatek.com>,
Yongqiang Niu <yongqiang.niu@mediatek.com>,
<linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-mediatek@lists.infradead.org>,
<Project_Global_Chrome_Upstream_Group@mediatek.com>
Subject: [PATCH v3 0/2] Add gce support for mt8188
Date: Fri, 4 Nov 2022 15:44:41 +0800 [thread overview]
Message-ID: <20221104074443.26172-1-Elvis.Wang@mediatek.com> (raw)
From: Elvis Wang <Elvis.Wang@mediatek.com>
Base on tag: next-20221028, linux-next/master
Change in v3:
- remove incorrect message.
Change in v2:
- use vendor in filename, use Dual license and remove inappropriate
define in mediatek,mt8188-gce.h
Elvis Wang (2):
dt-bingings: gce: add gce header file for mt8188
dt-bindings: mailbox: mediatek,gce-mailbox: add mt8188 compatible name
.../mailbox/mediatek,gce-mailbox.yaml | 1 +
include/dt-bindings/gce/mediatek,mt8188-gce.h | 966 ++++++++++++++++++
2 files changed, 967 insertions(+)
create mode 100644 include/dt-bindings/gce/mediatek,mt8188-gce.h
--
2.18.0
next reply other threads:[~2022-11-04 8:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-04 7:44 Elvis.Wang [this message]
2022-11-04 7:44 ` [PATCH v3 1/2] dt-bindings: gce: add gce header file for mt8188 Elvis.Wang
2022-11-04 9:12 ` AngeloGioacchino Del Regno
2022-11-06 10:27 ` Krzysztof Kozlowski
2022-11-07 11:18 ` Matthias Brugger
2022-11-22 9:10 ` Elvis Wang (王军)
2022-11-22 9:25 ` Krzysztof Kozlowski
2022-11-04 7:44 ` [PATCH v3 2/2] dt-bindings: mailbox: mediatek,gce-mailbox: add mt8188 compatible name Elvis.Wang
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=20221104074443.26172-1-Elvis.Wang@mediatek.com \
--to=elvis.wang@mediatek.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=devicetree@vger.kernel.org \
--cc=jason-jh.lin@mediatek.com \
--cc=jassisinghbrar@gmail.com \
--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=robh+dt@kernel.org \
--cc=yongqiang.niu@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).