From: Rob Herring <robh@kernel.org>
To: Jernej Skrabec <jernej.skrabec@siol.net>
Cc: mark.rutland@arm.com, devicetree@vger.kernel.org,
linux-sunxi@googlegroups.com, linux-kernel@vger.kernel.org,
mripard@kernel.org, wens@csie.org, robh+dt@kernel.org,
mchehab@kernel.org, linux-arm-kernel@lists.infradead.org,
linux-media@vger.kernel.org
Subject: Re: [PATCH 4/5] media: dt-bindings: media: Add Allwinner A64 deinterlace compatible
Date: Mon, 3 Feb 2020 15:50:53 +0000 [thread overview]
Message-ID: <20200203155053.GA25849@bogus> (raw)
In-Reply-To: <20200125110353.591658-5-jernej.skrabec@siol.net>
On Sat, 25 Jan 2020 12:03:52 +0100, Jernej Skrabec wrote:
>
> Allwinner A64 SoC also contains deinterlace core, compatible to H3.
>
> Add compatible string for it.
>
> Signed-off-by: Jernej Skrabec <jernej.skrabec@siol.net>
> ---
> .../bindings/media/allwinner,sun8i-h3-deinterlace.yaml | 6 +++++-
> 1 file changed, 5 insertions(+), 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:[~2020-02-03 15:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-25 11:03 [PATCH 0/5] arm64: dts: allwinner: a64: Enable deinterlace core Jernej Skrabec
2020-01-25 11:03 ` [PATCH 1/5] dt-bindings: interconnect: sunxi: Add A64 MBUS compatible Jernej Skrabec
2020-02-03 15:49 ` Rob Herring
2020-01-25 11:03 ` [PATCH 2/5] clk: sunxi-ng: a64: Export MBUS clock Jernej Skrabec
2020-01-25 11:03 ` [PATCH 3/5] arm64: dts: allwinner: a64: Add MBUS controller node Jernej Skrabec
2020-01-27 14:59 ` Maxime Ripard
2020-01-27 19:05 ` Jernej Škrabec
2020-01-25 11:03 ` [PATCH 4/5] media: dt-bindings: media: Add Allwinner A64 deinterlace compatible Jernej Skrabec
2020-02-03 15:50 ` Rob Herring [this message]
2020-01-25 11:03 ` [PATCH 5/5] arm64: dts: allwinner: a64: Add deinterlace core node Jernej Skrabec
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=20200203155053.GA25849@bogus \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jernej.skrabec@siol.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-sunxi@googlegroups.com \
--cc=mark.rutland@arm.com \
--cc=mchehab@kernel.org \
--cc=mripard@kernel.org \
--cc=robh+dt@kernel.org \
--cc=wens@csie.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).