From: Rob Herring <robh@kernel.org>
To: Alexander Stein <alexander.stein@mailbox.org>
Cc: Kevin Hilman <khilman@baylibre.com>,
Neil Armstrong <narmstrong@baylibre.com>,
linux-amlogic@lists.infradead.org,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
devicetree@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
Daniel Vetter <daniel@ffwll.ch>,
Jerome Brunet <jbrunet@baylibre.com>,
David Airlie <airlied@linux.ie>
Subject: Re: [PATCH v2 1/1] dt-bindings: display: meson-vpu: Add missing amlogic,canvas property
Date: Wed, 22 Dec 2021 13:29:21 -0400 [thread overview]
Message-ID: <YcNgceABXb03J9gN@robh.at.kernel.org> (raw)
In-Reply-To: <20211219094155.177206-1-alexander.stein@mailbox.org>
On Sun, 19 Dec 2021 10:41:55 +0100, Alexander Stein wrote:
> This property was already mentioned in the old textual bindings
> amlogic,meson-vpu.txt, but got dropped during conversion.
> Adding it back similar to amlogic,gx-vdec.yaml.
>
> Fixes: 6b9ebf1e0e67 ("dt-bindings: display: amlogic, meson-vpu: convert to yaml")
> Signed-off-by: Alexander Stein <alexander.stein@mailbox.org>
> ---
> Changes in v2:
> * Do not linebreak Fixes tag
> * Make amlogic,canvas mandatory as it was in textual binding already
> * Add amlogic,canvas to example
>
> .../devicetree/bindings/display/amlogic,meson-vpu.yaml | 6 ++++++
> 1 file changed, 6 insertions(+)
>
Acked-by: Rob Herring <robh@kernel.org>
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next prev parent reply other threads:[~2021-12-22 17:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-19 9:41 [PATCH v2 1/1] dt-bindings: display: meson-vpu: Add missing amlogic, canvas property Alexander Stein
2021-12-19 15:30 ` [PATCH v2 1/1] dt-bindings: display: meson-vpu: Add missing amlogic,canvas property Martin Blumenstingl
2021-12-20 14:12 ` Neil Armstrong
2021-12-22 17:29 ` Rob Herring [this message]
2022-01-03 11:16 ` Neil Armstrong
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=YcNgceABXb03J9gN@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=airlied@linux.ie \
--cc=alexander.stein@mailbox.org \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=jbrunet@baylibre.com \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=narmstrong@baylibre.com \
--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
all inboxes | Powered by JetHome®