From: Rob Herring <robh@kernel.org>
To: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
Cc: robh+dt@kernel.org, linux-arm-kernel@lists.infradead.org,
chunkuang.hu@kernel.org, jitao.shi@mediatek.com,
matthias.bgg@gmail.com, mcoquelin.stm32@gmail.com,
linux-mediatek@lists.infradead.org,
krzysztof.kozlowski@canonical.com,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
alexandre.torgue@foss.st.com, ck.hu@mediatek.com,
linux-stm32@st-md-mailman.stormreply.com, airlied@linux.ie,
daniel@ffwll.ch, p.zabel@pengutronix.de,
devicetree@vger.kernel.org, jason-jh.lin@mediatek.com
Subject: Re: [PATCH 1/3] dt-bindings: display: mediatek,mutex: Fix mediatek,gce-events type
Date: Fri, 4 Mar 2022 09:37:19 -0600 [thread overview]
Message-ID: <YiIyL+Vd1zWiDKbm@robh.at.kernel.org> (raw)
In-Reply-To: <20220304095458.12409-2-angelogioacchino.delregno@collabora.com>
On Fri, 04 Mar 2022 10:54:56 +0100, AngeloGioacchino Del Regno wrote:
> The mediatek,gce-events property needs as value an array of uint32
> corresponding to the CMDQ events to listen to, and not any phandle.
>
> Fixes: 4ed545e7d100 ("dt-bindings: display: mediatek: disp: split each block to individual yaml")
> Signed-off-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
> ---
> .../devicetree/bindings/display/mediatek/mediatek,mutex.yaml | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
Acked-by: Rob Herring <robh@kernel.org>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-03-04 15:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-04 9:54 [PATCH 0/3] Fix MediaTek display dt-bindings issues AngeloGioacchino Del Regno
2022-03-04 9:54 ` [PATCH 1/3] dt-bindings: display: mediatek, mutex: Fix mediatek, gce-events type AngeloGioacchino Del Regno
2022-03-04 15:37 ` Rob Herring [this message]
2022-03-04 23:43 ` Chun-Kuang Hu
2022-03-04 9:54 ` [PATCH 2/3] dt-bindings: display: mediatek, ovl: Fix 'iommu' required property typo AngeloGioacchino Del Regno
2022-03-04 15:37 ` [PATCH 2/3] dt-bindings: display: mediatek,ovl: " Rob Herring
2022-03-04 23:45 ` Chun-Kuang Hu
2022-03-04 9:54 ` [PATCH 3/3] dt-bindings: display: mediatek: Fix examples on new bindings AngeloGioacchino Del Regno
2022-03-04 15:39 ` Rob Herring
2022-03-04 23:47 ` Chun-Kuang Hu
2022-03-05 18:34 ` Jason-JH Lin
2022-03-09 3:42 ` Jason-JH Lin
2022-03-04 23:49 ` [PATCH 0/3] Fix MediaTek display dt-bindings issues Chun-Kuang Hu
2022-03-08 16:13 ` Rob Herring
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=YiIyL+Vd1zWiDKbm@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=airlied@linux.ie \
--cc=alexandre.torgue@foss.st.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=chunkuang.hu@kernel.org \
--cc=ck.hu@mediatek.com \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jason-jh.lin@mediatek.com \
--cc=jitao.shi@mediatek.com \
--cc=krzysztof.kozlowski@canonical.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=matthias.bgg@gmail.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=p.zabel@pengutronix.de \
--cc=robh+dt@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).